Regression between Maven 3.0 and Maven 2.2.1
--------------------------------------------
Key: MNBMODULE-102
URL: http://jira.codehaus.org/browse/MNBMODULE-102
Project: Maven NetBeans Module Plugin
Issue Type: Bug
Affects Versions: 3.3
Environment: Fedora Linux 13 64 bit, Windows XP SP3, JDK 6 update 21
Reporter: Jakub Herkel
Assignee: Jesse Glick
Attachments: test2.zip
We have found this problem, when we tried to test Maven 3.0 with our project.
With an older version we were able to compile the whole project without any
problem. With a new version we have a problem with nbm-maven-plugin. We could
see this :
[ERROR] Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:3.3:manifest
(default-cli) on project netrad.client.gui.module.core: See above for failures
in runtime NetBeans dependencies verification.
There is a little help that we should have a look above but unfortunately there
isn't any information why the building process failed. If we tried to run maven
with -X option, we could see :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.codehaus.mojo:nbm-maven-plugin:3.3:manifest (default-cli) on project
netrad.client.gui.module.core: See above for failures in runtime NetBeans
dependencies verification.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoFailureException: See above for failures
in runtime NetBeans dependencies verification.
at
org.codehaus.mojo.nbm.NetbeansManifestUpdateMojo.checkModuleClassPath(NetbeansManifestUpdateMojo.java:625)
at
org.codehaus.mojo.nbm.NetbeansManifestUpdateMojo.execute(NetbeansManifestUpdateMojo.java:447)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
... 19 more
I have prepared a demo project which shows this problem. Also I have found out
which dependency in pom.xml causes this problem. If I remove "test2.nvc.widget"
dependency from the module-core, everything is ok.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
