Unresolved dependencies in intermediate projects when using
dependencyManagement tag in multi-module builds
-----------------------------------------------------------------------------------------------------------
Key: MDEP-38
URL: http://jira.codehaus.org/browse/MDEP-38
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Affects Versions: 2.0-ALPHA1
Environment: maven-2.0.5-SNAPSHOT-20060917.124500
Reporter: Joseph Marques
I have a nested project with the follow structure:
root/intermediate1/intermediate2/leaf
In this setup, each child level is a module of the parent, and each child's POM
derives from the parent POM.
If I execute 'mvn help:effective-pom' at root or leaf, it works fine. However,
the following error message will be thrown when I try to validate the POM at
any intermediate level:
Validation Messages:
[0] 'dependencies.dependency.version' is missing for <DEP_1>
[...] 'dependencies.dependency.version' is missing for <DEP_...>
[N] 'dependencies.dependency.version' is missing for <DEP_N>
Reason: Failed to validate POM
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Failed to validate POM
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:370)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:283)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:120)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:263)
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)
Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to
validate POM
at
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:941)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:752)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:423)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:520)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:452)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:496)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:356)
... 11 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Sun Sep 17 10:33:24 EDT 2006
[INFO] Final Memory: 1M/127M
[INFO] ------------------------------------------------------------------------
This doesn't just affect the help:effective-pom goal; it throws this error
whenever it has to walk the dependency graph. So, for instance, I can't
execute 'mvn install' or 'mvn grafo:grafo'.
--
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
