Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-16025

Maven Dependency Processor does not resolve ${java.home}

    XMLWordPrintable

Details

    Description

      We have a project that imports BOMs from jboss (Kie, jbpm...) one of these boms has the artifact org.jboss:jboss-parent:11:jar as its parent.
      This POM has the following lines:

        <dependencyManagement>
          <dependencies>
            <dependency>
              <groupId>com.sun</groupId>
              <artifactId>tools</artifactId>
              <scope>system</scope>
              <version>1.6</version>
              <systemPath>${com.sun.tools.path}</systemPath>
            </dependency>
          </dependencies>
        </dependencyManagement>
      

      The property com.sun.tools.path is defined in the same POM as ${java.home}/../lib/tools.jar.
      When the Maven Dependency Processor Task is executed, it fails with the following message:

       error	10-Jun-2015 11:49:38	Automatic Maven plan dependencies processing failed: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
       [ERROR] 'dependencyManagement.dependencies.dependency.systemPath' for com.sun:tools:jar must specify an absolute path but is ${java.home}/../lib/tools.jar @ org.jboss:jboss-parent:11, D:\maven_repository\.m2\repository\org\jboss\jboss-parent\11\jboss-parent-11.pom, line 171, column 21
       [ERROR] 'dependencyManagement.dependencies.dependency.systemPath' for com.sun:tools:jar must specify an absolute path but is ${java.home}/../lib/tools.jar @ org.jboss:jboss-parent:11, D:\maven_repository\.m2\repository\org\jboss\jboss-parent\11\jboss-parent-11.pom, line 171, column 21
      

      I tried to override the value for com.sun.tools.path in the settings, but that doesn't seem to have any effect, not even in Maven (checked with help:effective-pom).

      I added a dependency management for the sun.com:tools before importing the boms, that results in a correct effective pom. but the dependency processor still fails with the same message

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              f5c7d0ddd00d Martin Goldhahn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: