Hi John,
I found something, but I can't ensure it is caused by 2.0.10-RC11. I
have a Maven plug-in that extends the lifecycle and adds a new kind of
package. It also uses some Ant tasks. When I build the plug-in with
2.0.10-RC* (I tried with RC1, RC2 and RC11) the build works. But when I
try to build a project that depends upon this plug-in and use my custom
package, I get an "required goal not found" error (below is the entire
exception message).
I have no problems if I build the plug-in with 2.0.9. You can access the
code of this plug-in on [1].
[1]https://svn.objectstyle.org/repos/woproject/trunk/woproject/maven2/maven-wolifecycle-plugin
Cheers,
Henrique
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Required goal not found:
org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:woframework in
org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.16-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: Required goal not found:
org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:woframework in
org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.16-SNAPSHOT
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1820)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1295)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1259)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:516)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:369)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
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:585)
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)
[INFO]
------------------------------------------------------------------------
John Casey wrote:
Hi again,
One bug was identified in 2.0.10-RC10 last Friday night. This release
candidate addresses that issue. You can find it here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/
Please give this a spin when you get a chance, and let us know if you
find any problems. We'll file any issues in JIRA against version 2.0.10
for tracking purposes, and to give us a JIRA # to use when writing the
integration test to verify the fix.
Thanks,
-john
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
