Uploaded image for project: 'Maven Shared Components'
  1. Maven Shared Components
  2. MSHARED-101

NPE in DefaultDependencyTreeBuilder when using version ranges.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: maven-dependency-tree-1.2
    • Fix Version/s: None
    • Component/s: maven-dependency-tree
    • Labels:
      None
    • Environment:
      vista

      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.

        Attachments

        1. maven-dependency-tree.patch
          3 kB
          Will Horn
        2. bundle-all-test.zip
          2 kB
          Will Horn
        3. maven-dependency-tree-fix
          4 kB
          Will Horn

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                will.horn@gmail.com Will Horn
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: