maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From S├ębastien Arbogast (JIRA) <>
Subject [jira] Created: (MPIDEA-47) Unnecessary request for version number in dependencyManagement section
Date Tue, 22 Aug 2006 22:48:48 GMT
Unnecessary request for version number in dependencyManagement section

                 Key: MPIDEA-47
             Project: maven-idea-plugin
          Issue Type: Bug
    Affects Versions: 1.7
            Reporter: S├ębastien Arbogast

I have a root POM with a dependencyManagement section that specifies all the version numbers
for dependencies. And in an "app" module below, I have another POM where the dependencyManagement
section is used to specify dependency exclusions, but none of these dependencies specify a
version number as it's supposed to be inherited from the parent (root) POM dependencyManagement

Yet, when I try to run "mvn idea:idea" on the root project, I get a build failure in the "app"
module saying that the version for the dependencies cannot be null. The thing is that it CAN
be null: that's what dependencyManagement inheritance is made for. The best proof of that
is that "mvn install" on the whole project runs fine.

I added version numbers to those dependencies and it fixed the issue, but I shouldn't have
to repeat them since they are already specified in the root POM's dependencyManagement section.
Moreover, I'm using a project generator (AndroMDA) that generates all the POM's for me and
it doesn't include version numbers at this level.

I hope I was clear enough :oP

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