I found if I modify the execute to add an or on the packaging being pom, it will skip the top pom, and still execute for each of the children. I'm not sure if this is the right spot for this.
See MCLIRR-28 -- Larry On Wed, Apr 28, 2010 at 11:04 AM, Larry Shatzer, Jr. <[email protected]> wrote: > > I have a multi module project that I want to run the clirr plugin on, and it > is failing on the top pom. here is the output: > mvn clirr:check > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] Project A > [INFO] Project A - Submodule 1 > [INFO] Project A - Submodule 2 > [INFO] > ------------------------------------------------------------------------ > [INFO] Building Project A > [INFO] task-segment: [clirr:check] > [INFO] > ------------------------------------------------------------------------ > [INFO] Preparing clirr:check > [INFO] [clirr:check {execution: default-cli}] > [INFO] Comparing to version: 1.4.1 > [INFO] > ------------------------------------------------------------------------ > [ERROR] FATAL ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Cannot open > /Users/lshatzer/.m2/repository/com/xyz/project-a/1.4.1/project-a-1.4.1.pom > for reading > error in opening zip file > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > net.sf.clirr.core.CheckerException: Cannot open > /Users/lshatzer/.m2/repository/com/xyz/project-a/1.4.1/project-a-1.4.1.pom > for reading > at > net.sf.clirr.core.internal.bcel.BcelTypeArrayBuilder.createClassSet(BcelTypeArrayBuilder.java:73) > at > org.codehaus.mojo.clirr.AbstractClirrMojo.resolvePreviousReleaseClasses(AbstractClirrMojo.java:306) > at > org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:192) > at > org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:182) > at org.codehaus.mojo.clirr.ClirrCheckMojo.execute(ClirrCheckMojo.java:68) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: java.util.zip.ZipException: error in opening zip file > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:114) > at > net.sf.clirr.core.internal.bcel.BcelTypeArrayBuilder.createClassSet(BcelTypeArrayBuilder.java:69) > ... 23 more > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 4 seconds > [INFO] Finished at: Wed Apr 28 10:35:30 MDT 2010 > [INFO] Final Memory: 33M/264M > [INFO] > ------------------------------------------------------------------------ > It looks like it is trying to open the jar file (even though it says it can't > open the pom file, which does exist). The jar file won't exists for this, > since it's packaging type is "pom", since it is the top level pom for this > multi-module project. > -- Larry --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
