In Bamboo 3.1 we started adding the JDK location to the PATH variable;
PATH=/tmp/ PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home/bin
If I define a PATH variable in my build, the value doesn't take affect as the JDK PATH value takes precedence;
2011-06-06 16:33:46,103 INFO [1-BAM::Default Agent::Agent:pool-7-thread-1] [ProcessServiceImpl] Beginning to execute external process for build 'ORGTEST - SOME - Default Job'<br /> ... running command line: /Applications/dev/apache-maven-2.1.0/bin/mvn clean test<br /> ... in : /atlassian/Bamboo/Bamboo/Bamboo31/homes/xml-data/build-dir/ORGTEST-SOME-JOB1<br /> ... using extra environment variables: MAVEN2_HOME=/Applications/dev/apache-maven-2.1.0 JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home M2_HOME=/Applications/dev/apache-maven-2.1.0 PATH=MY_VAR PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home/bin
Bug
Low
