[
https://jira.codehaus.org/browse/MSHARED-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSHARED-101.
----------------------------------
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.
> NPE in DefaultDependencyTreeBuilder when using version ranges.
> --------------------------------------------------------------
>
> Key: MSHARED-101
> URL: https://jira.codehaus.org/browse/MSHARED-101
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree-1.2
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
