www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Mazza <glen.ma...@gmail.com>
Subject Maven "latest" ain't the latest anymore
Date Wed, 31 Jul 2013 10:51:10 GMT
Hi, when I configure my Roller Maven builds and choose "Maven (latest)", 
i.e., a desire to see the app run successfully on the newest Maven you 
have loaded, no matter what, I'm not getting the latest available 
(3.0.4) but just the old 2.2.1:

[Roller] $ /home/hudson/tools/java/latest1.6/bin/java -cp
/home/jenkins/jenkins-slave/maven-agent.jar:/home/jenkins/jenkins-slave/classworlds.jar
hudson.maven.agent.Main /home/hudson/tools/maven/apache-maven-2.2.1
/home/hudson/jenkins-slave/slave.jar
/home/jenkins/jenkins-slave/maven-interceptor.jar 60722
/home/jenkins/jenkins-slave/maven2.1-interceptor.jar


No problem for me, I'll go back to what I had it for -- Maven 3.0.4 
explicitly.

Might it be good to update the definition of "Maven (latest)" to 3.0.4; 
or, alternatively, if it's a bad idea anyway to rely on a non-specific 
Maven build version (and it may be, idk), just remove the Maven (latest) 
option?  (Although I don't know which Maven version would be used for 
those still on it.)

Incidentally, no big deal for me but when do you plan on loading Maven 
3.0.5?  A new plugin I'd like to rely on unfortunately requires it 
(although I think I need to issue a bug report to that plugin for 
erroneously requiring that modern a version.)

Thanks,
Glen


Mime
View raw message