maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Marques (JIRA)" <>
Subject [jira] Created: (MDEP-38) Unresolved dependencies in intermediate projects when using dependencyManagement tag in multi-module builds
Date Sun, 17 Sep 2006 15:18:11 GMT
Unresolved dependencies in intermediate projects when using dependencyManagement tag in multi-module

                 Key: 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:


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(
        at org.apache.maven.DefaultMaven.doExecute(
        at org.apache.maven.DefaultMaven.execute(
        at org.apache.maven.cli.MavenCli.main(
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.codehaus.classworlds.Launcher.launchEnhanced(
        at org.codehaus.classworlds.Launcher.launch(
        at org.codehaus.classworlds.Launcher.mainWithExitCode(
        at org.codehaus.classworlds.Launcher.main(
Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to validate POM
        at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(
        at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(
        at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(
        at org.apache.maven.DefaultMaven.getProject(
        at org.apache.maven.DefaultMaven.collectProjects(
        at org.apache.maven.DefaultMaven.collectProjects(
        at org.apache.maven.DefaultMaven.getProjects(
        ... 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:
For more information on JIRA, see:


View raw message