Could you have a look in the "Logs" tab for the build that should be using 2.0.5. The first lines of the log should display exactly what command Bamboo is running. Is it trying to use 2.0.5 there?

Is there MAVEN2_HOME or a M2_HOME that may be pointing to the old Maven?

We'll try to reproduce it locally here and see if we can find out anything.

Cheers

Mark C

It's using m2.0.5. There is no preconfigured M2_HOME for the user Bamboo is running under. There is however, another maven2 builder in Bamboo configured, using m2.0.4, if that matters.

Andrew

This is very strange. In the logs for each build there should be

Starting to build 'Confluence - Unit Tests'
... running command line: /opt/java/tools/maven2/bin/mvn clean test -Pcore,bamboo
... in : /opt/bamboo/xml-data/build-dir/CONF-MAIN
... using java: /usr/java/j2sdk/
... using environment variables: MAVEN_OPTS=-Xmx256M

which specifies exactly which executable is being run. (in the above case /opt/java/tools/maven2/bin/mvn). So if you've made sure that this is already pointing to 2.0.5, then I'm not 100% sure what may be going on here.

If you could run your Maven target and append the "-X" flag, which should output the version of the Maven executable, that may give us information. Could you attach the log (from the log tab of your build) to this issue after running it was the -X flag?

Cheers,

Mark C

Is this still a problem for you? Did you get any chance to run the debugging Maven command? If so, can you please attach the output to this issue?

Otherwise, we might close the issue.

Cheers,

Mark C