Activity

Caused by: org.apache.maven.plugin.PluginExecutionException: Execution clirr-check of goal org.codehaus.mojo:clirr-maven-plugin:2.7:check failed: Invalid byte tag in constant pool: 18
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more
Caused by: org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 18
at org.apache.bcel.classfile.Constant.readConstant(Constant.java:146)
at org.apache.bcel.classfile.ConstantPool.<init>(ConstantPool.java:67)
at org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:222)
at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:136)
at org.apache.bcel.util.ClassLoaderRepository.loadClass(ClassLoaderRepository.java:94)
at org.apache.bcel.classfile.JavaClass.getInterfaces(JavaClass.java:788)
at org.apache.bcel.classfile.JavaClass.getAllInterfaces(JavaClass.java:804)
at net.sf.clirr.core.internal.bcel.BcelJavaType.getAllInterfaces(BcelJavaType.java:78)
at net.sf.clirr.core.internal.checks.InterfaceSetCheck.check(InterfaceSetCheck.java:58)
at net.sf.clirr.core.Checker.runClassChecks(Checker.java:190)
at net.sf.clirr.core.Checker.reportDiffs(Checker.java:136)
at org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:739)
at org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:307)
at org.codehaus.mojo.clirr.AbstractClirrCheckMojo.doExecute(AbstractClirrCheckMojo.java:74)
at org.codehaus.mojo.clirr.AbstractClirrMojo.execute(AbstractClirrMojo.java:243)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

Vincent Massol
added a comment - 15/Mar/16 10:45 - edited Starting a comparison that I'll update as I progress (note that I'm not reporting bugs here as they are being fixed):
revapi:
only java 8
no way to specify def of artifact compared centrally for all cases (issue with packaging type = maven-archetype). Lukas said he's thinking about addressing this.
nicer reporting of errors directly in the maven logs and no extra files generated
only reports backward incompatibilities
ok when no previous version exists. However no warning printed, nothing printed at all. Could be improved
a few bugs found and fixed quickly after reported)
great support
awkward maven configuration using JSON (not able to perform maven inheritance leading to having to duplicate default excludes for internal and test packages)
TODO: speed test
japicmp
java 8 but works also on java 7
no way to specify def of artifact compared centrally for all cases (issue with packaging type = maven-archetype)
need to open file to see the errors (diff, xml or html).
report all changes in the files (even changes that are not backward incompatible)
several bugs founds (and fixed quickly after reported) but still shows a greater lack of maturity
great support
better maven configuration
TODO: speed test

Vincent Massol
added a comment - 05/Apr/16 14:59 Documented in lots of places on xwiki.org; only one place remaining: http://dev.xwiki.org/xwiki/bin/view/ReleasePlans/ReleasePlanHelp#HGenerateBackwardCompatibilityReport