I ran a Maven build this morning and it broke. Strange, as I had not changed anything. Maven’s ability to simply break because of a change to a non-versioned dependency or even more arcane, a versioned dependency with a non-versioned dependency of it’s own (a transitive dependency) is legendary. So I thought that was the trouble. On my other machine I ran a build and the Maven output “looked” different. Stranger still. So I did a mvn version on both.
Whoa! My Big Mac was 2.11 and my MacBook Pro was 3.0.2.
Apache Maven 3.0.2 (r1056850; 2011-01-09 10:58:10+1000) Java version: 1.6.0_24, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x", version: "10.6.6", arch: "x86_64", family: "mac"
It came down in the “Java for Mac OS X 10.6 Update 4” which was released on 10 March.
Now a lot of folks are not ready to move to 3. For myself firstly I don’t need the grief until it is rock solid. Secondly, I use the site plugin and reporting extensively and this is all getting a big makeover in 3 which is not yet done.
There are lots of ways to go back to your old version.
My was is to add the old version into the front of my PATH in .bash_profile:
export PATH=/Users/gluck/work/apache-maven-2.2.1/bin:$PATH