New Jnario Release 0.6.0

[Sebastian Benz]

Hello everyone,

there is a new Jnario release 0.6.0 available. This is a small release containing some minor bug fixes and adding the compatibility to the latest Xtend release 2.4.3. The fixes are in detail: 

• Compatible with Xtend 2.4.3

• Fix: encoding problems in generated reports

• Fix: CompilerMain & ReportGeneratorMain return error code if compilation fails.

• Fix: remove invalid validation error when two root specs both reference java types.

Happy testing!

Sebastian

---
@sebabenz
www.sebastianbenz.de

[Jeremy]

Hi Seb,

is this in Maven anywhere? I can see it via Eclipse's auto-update, but Maven http://mvnrepository.com/artifact/org.jnario/jnario-maven-plugin doesn't seem to know about it.

[Sebastian Benz]

Hello Jnario,

the release got stuck during the maven release process, but it is available now.

Cheers,

Sebastian  

--
You received this message because you are subscribed to the Google Groups "Jnario" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jnario+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Jeremy]

Thanks, unfortunately it doesn't work... I'm getting a "Execution default of goal org.jnario:jnario-maven-plugin:0.6.0:testCompile failed: path is
not absolute". Running maven with -e, the stack trace below seems to suggest it's a problem in JnarioTestCompile.compile

[ERROR] Failed to execute goal org.jnario:jnario-maven-plugin:0.6.0:testCompile (default) on project
 KayTwo: Execution default of goal org.jnario:jnario-maven-plugin:0.6.0:testCompile failed: path is
not absolute -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.jnario:jnario-mav
en-plugin:0.6.0:testCompile (default) on project KayTwo: Execution default of goal org.jnario:jnario
-maven-plugin:0.6.0:testCompile failed: path is not absolute
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
ilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
ilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter
.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:318)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default of goal org.jnario:jn
ario-maven-plugin:0.6.0:testCompile failed: path is not absolute
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.j
ava:115)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        ... 19 more
Caused by: java.lang.IllegalStateException: path is not absolute
        at org.eclipse.xtend.lib.macro.file.Path.getParent(Path.java:129)
        at org.eclipse.xtend.core.compiler.batch.XtendBatchCompiler.configureWorkspace(XtendBatchCom
piler.java:261)
        at org.eclipse.xtend.core.compiler.batch.XtendBatchCompiler.compile(XtendBatchCompiler.java:
273)
        at org.jnario.maven.JnarioTestCompile.compile(JnarioTestCompile.java:157)
        at org.eclipse.xtend.maven.XtendTestCompile.compileTestSources(XtendTestCompile.java:63)
        at org.jnario.maven.JnarioTestCompile.compileXtendSources(JnarioTestCompile.java:78)
        at org.jnario.maven.JnarioTestCompile.internalExecute(JnarioTestCompile.java:68)
        at org.eclipse.xtend.maven.AbstractXtendMojo.execute(AbstractXtendMojo.java:39)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.j
ava:106)

[Sebastian Benz]

I will have a look at it over the weekend.

Cheers,

Sebastian

[Boris Brodski]

Hi Jeremy,

Hi Sebastian,

the problem is in Xtend. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=417177.

It is already fixed in master branch: https://git.eclipse.org/r/#/c/16551/.

The problem occur only, if you do headless build on Windows.

Cheers,

Boris

[Sebastian Benz]

Thanks Boris for lettings us know. I integrated the fix into the latest maven snapshot.

Cheers,

Sebastian

--

[Jeremy]

Hi Seb,

I've taken the latest from here https://oss.sonatype.org/content/repositories/snapshots/org/jnario/org.jnario.standalone.maven/1.0.0-SNAPSHOT/ , timestamped at 06:11.

I'm getting a warning that the pom is invalid, so transitive dependencies are not available; then the build fails with the path not absolute warning.

From looking at the standalone pom, it's set to use xtend 2.4.2 instead of 2.4.3?

[Sebastian Benz]

Thanks for the hint. It's fixed now. 

Sebastian

[Jeremy]

I'm afraid that's still not worked.

I can build using Jnario 0.5.1 and xtend 2.4.3 , but when I try jnario 1.0.0-snapshot it's still giving the same error.

I've got Maven debug logs which I can email to you if you'd like, comparing the jnario 0.5.1 to 1.0.0 output.

n.b. I'm behind a corporate firewall using a sonatype nexus maven repository so I'll try from home this weekend using a direct connection to central; however I'd be surprised if that is the fault seeing as I can compile Jnario 0.5.1 on xtend 2.4.3.

[Sebastian Benz]

Did you force an snapshot update using "mvn clean test -U", because I found the reason for the problem you described and fixed it in the latest snapshot. If you still have the problems, it would be helpful if you could send me your debug logs.

Sebastian

[Jeremy]

I can't pull down snapshots "easily" because of network restrictions. Instead I've had to manually download the snapshots and load them into my local m2 repo.

I've pulled the snapshots from here https://oss.sonatype.org/content/repositories/snapshots/org/jnario/org.jnario.standalone.maven/1.0.0-SNAPSHOT/ stamped "1.0.0-20130927.193741-4", and repeated that for each of the requirements. I'll send the log files over now.

[Jeremy]

I've also checked the version of xtend 2.4.3-SNAPSHOT, and the last time I tried to run, it used a version from 30th Sept.

log.txt is using 1.0.0-SNAPSHOT
logOld.txt is using 0.5.1

[Jeremy]

Hi Seb, I've finally had the chance to run this from my personal pc (so not restricted to what I can download via maven)

I believe I've found the offending piece of code for you; unfortunately if I'm right, you'll need to get a bug raised against xTend before you can use it as you intend.

This line in org.eclipse.xtend.lib.macro.file.Path Path(String pathAsString) constructor is not deciphering an absolute path correctly for Windows:

// if the first element is empty it has a leading separator;
this.absolute = iterable.iterator().next().length() == 0;

For the path "D:/Programming/Java/jNarioInvestagitive/src/test/java" (what's been set as the SourcePath in JnarioTestCompile ( xtend2BatchCompiler.setSourcePath(concat(File.pathSeparator, newArrayList(filtered))); ), the first element is returning as "D:", as such the length is NOT 0, so it's not resolving as an absolute path, hence then failing in XtendBatchCompiler.configureWorkspace while loop "commonRoot = commonRoot.getParent();" - the getParent() line will throw an exception if it's not an absolute path.

This is on the very latest xtend 2.4.3-SNAPSHOT & jnario 1.0.0-SNAPSHOT, I've also done a quick test on the 2.5.0-SNAPSHOT and have the same results.

[Sebastian Benz]

Hi Jeremy,

thanks for looking into it. This is definitely something that needs to be fixed in Xtend. However, I would strongly advice you against using absolute paths in your build files, as these make your projects hard to share and maintain. It might be even a feature of Xtend forcing you to use relative paths. ;-)

Cheers,

Sebastian

--

[Jeremy]

Hi Seb,

I'd agree, except I'm not. Maven substitutes the paths. The pom I've used to replicate is attached.

If you want, I can upload a sample project replicating the issue.

[Jeremy]

I've just re-run using your latest 1.0.0-SNAPSHOT and it appears to be fixed now. 0.6.1 still has the fault.

Cheers,
Jeremy

[Sebastian Benz]

That’s good news. I will think about making another 0.6.2 release including these fixes as well.

Sebastian

[Jeremy]

HI Seb, any news on this, or on progress to the 1.0.0 release?

[Sebastian Benz]

Hello Jeremy.

I plan to release 1.0.0 in December after the xtext 2.5 release.

Sebastian

[Stefan Oehme]

Any updates on 1.0.0? I'd like to migrate my projects to Xtend 2.5, but that's not possible with Jnario 0.6.1

[Peter Friese]

Same here. 

[Sebastian Benz]

Hello everyone,

sorry for the the long silence. I was absolutely swamped with work in November/December and had no time to work on the new features for the 1.0 release. I am thinking about releasing a 0.7.0 version in the next days which provides compatibility with Xtend 2.5. 

I am sorry for any inconveniences,

Sebastian

[Stefan Oehme]

That would be great =)

2014/1/5 Sebastian Benz <sebasti...@gmail.com>

--
You received this message because you are subscribed to a topic in the Google Groups "Jnario" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jnario/JGtJb72Qc3Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jnario+un...@googlegroups.com.