[ 
https://jira.codehaus.org/browse/MIDEA-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MIDEA-65.
-------------------------------

    Resolution: Won't Fix

Please refer to 
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
 if you're wondering why this issue was closed out.

> Unnecessary request for version number in dependencyManagement section
> ----------------------------------------------------------------------
>
>                 Key: MIDEA-65
>                 URL: https://jira.codehaus.org/browse/MIDEA-65
>             Project: Maven IDEA Plugin (RETIRED)
>          Issue Type: Bug
>            Reporter: Sebastien 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 section. 
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to