Olaf,
It is possible that one of the dependencies is not explicitly
specified, either directly of from its parent projects. Please open JIRA
issue and attach example project that would allow us to reproduce this
issue. See some hints at
http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues
regards,
Eugene
Olaf Bergner wrote:
I have several projects that use a maven-jar-plugin:2.1 declared in their
parent pom. As long as I build each project separately, this works like a
charm. If, however, I run m2eclipse in reactor mode - starting maven 2.0.7
from the commandline works - my build fails:
[ERROR] BUILD FAILURE com.obergner.osgi.server:jndi.osgi:jar:1.0-SNAPSHOT (
task-segment: [clean, install] )
[INFO]
----------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-jar-plugin:2.2-SNAPSHOT:jar': Unable to find
the mojo 'org.apache.maven.plugins:maven-jar-plugin:2.2-SNAPSHOT:jar' in the
plugin 'org.apache.maven.plugins:maven-jar-plugin'
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in
the plugin manager executing goal
'org.apache.maven.plugins:maven-jar-plugin:2.2-SNAPSHOT:jar': Unable to find
the mojo 'org.apache.maven.plugins:maven-jar-plugin:2.2-SNAPSHOT:jar' in the
plugin 'org.apache.maven.plugins:maven-jar-plugin'
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
ures(DefaultLifecycleExecutor.java:526)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa
ultLifecycleExecutor.java:342)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
Executor.java:165)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:227)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:871)
at
org.maven.ide.eclipse.embedder.Maven2Executor.main(Maven2Executor.java:85)
Caused by: org.apache.maven.plugin.PluginContainerException: Unable to find
the mojo 'org.apache.maven.plugins:maven-jar-plugin:2.2-SNAPSHOT:jar' in the
plugin 'org.apache.maven.plugins:maven-jar-plugin'
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPlugin
Manager.java:823)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
r.java:647)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
ures(DefaultLifecycleExecutor.java:519)
... 5 more
Caused by:
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Component descriptor cannot be found in the component repository:
org.apache.maven.plugin.Mojo
[org.apache.maven.plugins:maven-jar-plugin:2.2-SNAPSHOT:jar] (lookup realm:
ClassRealm[com.obergner.osgi.server:jndi.osgi:1.0-SNAPSHOT/plugins/org.apach
e.maven.plugins:maven-jar-plugin, parent:
ClassRealm[com.obergner.osgi.server:jndi.osgi:1.0-SNAPSHOT, parent:
ClassRealm[plexus.core, parent: null]]]).
at
org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLoo
kupManager.java:139)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.jav
a:500)
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPlugin
Manager.java:819)
... 7 more
What puzzles me is that m2eclipse resolves maven-jar-plugin to 2.2-SNAPSHOT,
not 2.1. This happens even if I copy the maven-jar-plugin configuration from
the parent pom into the failing project.
This used to work in m2eclipse 0.11.0 and now breaks after upgrading to
0.12.0. At least I'm quite sure about that. I couldn't verify this since
when trying to downgrade to 0.11.0 I made some mistake which left me with a
dysfunctional m2eclipse installation. Any pointers?
Cheers,
Olaf
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
