[jira] Updated: (MNG-4159) NPE in DefaultDependencyTreeBuilder when using version ranges.

["Will Horn (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will Horn updated MNG-4159:
---------------------------

    Attachment: maven-dependency-tree-fix

Potential fix/hack.  Uses getVersionRange instead of getBaseVersion in the map key.

> NPE in DefaultDependencyTreeBuilder when using version ranges.
> --------------------------------------------------------------
>
>                 Key: MNG-4159
>                 URL: http://jira.codehaus.org/browse/MNG-4159
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.9
>         Environment: vista
>            Reporter: Will Horn
>         Attachments: bundle-all-test.zip, maven-dependency-tree-fix, maven-dependency-tree.patch
>
>
> DefaultDependencyTreeBuilder does not seem to handle managed version ranges.  I have attached a JUnit test that throws the NPE.
> I ran into this issue when using the maven-bundle-plugin, which uses DefaultDependencyTreeBuilder.  I've also attached the full maven project that reproduces this.  The scenario is:
> bundle-all-test: root project, defines dependency on log4j with a *version range* and runtime scope in dependencyManagement 
> proj1: jar project depending on log4j, reducing scope to compile 
> proj2: pom project depending on proj1
> To reproduce, run 'mvn org.apache.felix:maven-bundle-plugin:bundleall' in the proj2 directory.

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