You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Barrie Treloar <ba...@gmail.com> on 2007/01/25 01:01:27 UTC
[DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: default. ???
My pom is using a
<packaging>zip</packaging>
to bind the
<groupId>org.codehaus.mojo</groupId>
<artifactId>pde-maven-plugin</artifactId>
for building an Eclipse RCP.
Any ideas where I start to look for resolving this problem?
It appears to only fail in an reactor build.
If I run this from within the module it fires of pde-maven-plugin correctly.
This may be an edge case because my computer is fresh and clean and if
I let the project complete successfully it may work as expected but be
hiding this problem.
Note the "zip" appended to the debug message.
[DEBUG] Error looking up lifecycle mapping to retrieve optional mojos.
Lifecycle ID: default. Error: Component descriptor cannot be found in
the component repository:
org.apache.maven.lifecycle.mapping.LifecycleMappingzip.
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Component descriptor cannot be found in the
component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingzip.
at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
at org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptionalMojosForLifecycle(DefaultLifecycleExecutor.ja
va:1106)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:9
94)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:
975)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:453)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
a:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
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:324)
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)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: default. ???
Posted by Barrie Treloar <ba...@gmail.com>.
There is something wrong with dependency resolution.
If I comment out the module build from my parent pom things work.
I will see if I can put together a test case.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: default. ???
Posted by Barrie Treloar <ba...@gmail.com>.
> The symptom appears to be
> * the pde build is not run.
> * the pde build fails because is is missing a dependency to itself
> <groupId>:<artifactId>:zip:0.5-SNAPSHOT
> * the path to this missing dependency is from the NEXT module the
> "build" module that creates all the assemblies.
> Path to dependency:
> 1) <groupId>:build:pom:0.5-SNAPSHOT
> 2) <groupId>:<artifactId>:zip:0.5-SNAPSHOT
Looking through the stack trace from -X isn't helping as there is
nothing to indicate why this artifact is selected for resolution.
[DEBUG] <groupId>:build:pom:0.5-SNAPSHOT (selected for null)
[DEBUG] <groupId>:<artifactId>:zip:0.5-SNAPSHOT:compile (selected for compile)
I think indicates that the build project will not resolve dependencies.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: default. ???
Posted by Barrie Treloar <ba...@gmail.com>.
I've seen the thread
http://www.nabble.com/forum/ViewPost.jtp?post=4827726&framed=y&skin=177
but I have
<extensions>true</extensions>
already.
Maybe this isn't the problem.
The symptom appears to be
* the pde build is not run.
* the pde build fails because is is missing a dependency to itself
<groupId>:<artifactId>:zip:0.5-SNAPSHOT
* the path to this missing dependency is from the NEXT module the
"build" module that creates all the assemblies.
Path to dependency:
1) <groupId>:build:pom:0.5-SNAPSHOT
2) <groupId>:<artifactId>:zip:0.5-SNAPSHOT
which makes no sense.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org