Low The maven dependency processor fails with the error below if we use variable paths:
Automatic Maven plan dependencies processing failed: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[ERROR] 'dependencies.dependency.systemPath' for java:plugin.jar:jar must specify an absolute path but is ${java.home}\lib\plugin.jar @ line 23, column 16
05-Feb-2013 18:39:30 Finished task 'Maven Dependencies Processor'
Basically I replicate the issue by adding the below dependency to my pom.xml and configuring the processor task:
<dependency>
<groupId>java</groupId>
<artifactId>plugin.jar</artifactId>
<systemPath>${java.home}/lib/plugin.jar</systemPath>
<version>$
{java.version}
</version>
<scope>system</scope>
</dependency>
Substituting java.home with the absolute path fixes the issue. Again running the command mvn help:effective-pom from DOS does indeed substituted correctly.
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[BAM-12775] The Maven dependency processor not able to expand paths
Krzysztof Reisner
added a comment - We also encounter the same problem. This is a huge blocker for us because fixing by giving an absolute path is not an option. Currently we are using our own nexus repository and changes there any pom sounds like huge anti-pattern. If you could diagnose and fix that would be great, because as I'm said before this really really blocks our Continuous Delivery process.
Krzysztof Reisner
added a comment - We also encounter the same problem. This is a huge blocker for us because fixing by giving an absolute path is not an option. Currently we are using our own nexus repository and changes there any pom sounds like huge anti-pattern. If you could diagnose and fix that would be great, because as I'm said before this really really blocks our Continuous Delivery process. 
Yves Flückiger
added a comment - We encounter the same problem as Stephan as we are also using JavaFX.
Setting the <systemPath> absolute is not an option as we are also building from workstations with different java home using the same pom.
Yves Flückiger
added a comment - We encounter the same problem as Stephan as we are also using JavaFX.
Setting the <systemPath> absolute is not an option as we are also building from workstations with different java home using the same pom. 
Adam Barna
added a comment - I'm surprised more customers are not complaining about this. This build is breaking my builds and the "fix" for it is to give it an absolute, hard coded path which breaks builds on other systems. It's a major bug since it is a glaring shortcoming relative to the competition and there is no workaround that I am aware of that does not break a well designed build system. Please fix this!
Adam Barna
added a comment - I'm surprised more customers are not complaining about this. This build is breaking my builds and the "fix" for it is to give it an absolute, hard coded path which breaks builds on other systems. It's a major bug since it is a glaring shortcoming relative to the competition and there is no workaround that I am aware of that does not break a well designed build system. Please fix this! 
Stephan
added a comment - I'm having the same problem when trying to build a project containing JavaFX (Bamboo 5.0.1):
<dependency>
<groupId>javafx</groupId>
<artifactId>javafx</artifactId>
<version>2.1</version>
<scope>system</scope>
<systemPath>${java.home}/lib/jfxrt.jar</systemPath>
</dependency>
Results in this error:
Automatic Maven plan dependencies processing failed: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[ERROR] 'dependencies.dependency.systemPath' for javafx:javafx:jar must specify an absolute path but is ${java.home}/lib/jfxrt.jar @ line 57, column 16
"${java.home}" is not expanded during dependency processing. Trying to set these as plan-variables had no effect 
Stephan
added a comment - I'm having the same problem when trying to build a project containing JavaFX (Bamboo 5.0.1):
<dependency>
<groupId>javafx</groupId>
<artifactId>javafx</artifactId>
<version>2.1</version>
<scope>system</scope>
<systemPath>${java.home}/lib/jfxrt.jar</systemPath>
</dependency>
Results in this error:
Automatic Maven plan dependencies processing failed: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [ERROR] 'dependencies.dependency.systemPath' for javafx:javafx:jar must specify an absolute path but is ${java.home}/lib/jfxrt.jar @ line 57, column 16
"${java.home}" is not expanded during dependency processing. Trying to set these as plan-variables had no effect
This issue seems to have the same root cause as
BAM-16025