Maven Shared Components
  1. Maven Shared Components
  2. MSHARED-101

NPE in DefaultDependencyTreeBuilder when using version ranges.

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: maven-dependency-tree-1.2
    • Fix Version/s: None
    • Component/s: maven-dependency-tree
    • Labels:
      None
    • Environment:
      vista
    • Number of attachments :
      3

      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

          Activity

          Hide
          Will Horn added a comment - - edited

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

          <uploaded maven-dependency-tree-fix>

          Show
          Will Horn added a comment - - edited Potential fix/hack. Uses getVersionRange instead of getBaseVersion in the map key. <uploaded maven-dependency-tree-fix>

            People

            • Assignee:
              Unassigned
              Reporter:
              Will Horn
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: