[MSHARED-101] NPE in DefaultDependencyTreeBuilder when using version ranges.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: maven-dependency-tree-1.2
• Component/s: maven-dependency-tree
• Environment: vista
• Assignee: Unassigned
• Reporter: Will Horn
• Created: 12/May/09 12:42
• Updated: 25/Nov/14 14:49
• Resolved: 25/Nov/14 14:49

Description

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.

Issue Links

• is duplicated by: MSHARED-77 DependencyTreeResolutionListener throws NullPointerException
• relates to: MSHARED-77 DependencyTreeResolutionListener throws NullPointerException