On 09/10/2012 03:12 PM, Olivier Lamy wrote:
I prefer animal-sniffer to toolchains
Sure, it is cleaner, so long as you do not need to run tests on an older VM.
having to create/maintain a file ~/.m2/toolchains.xml is a pain. At least jenkins could create it
Good point, the Maven plugin ought to be smart enough to notice your build uses toolchains, and set things up according to the JDK selected for the project, with whatever the local path is on the current node. Do enough people use toolchains to make this worthwhile?
My concern is not me but the majority of the users who have 1.5 build with maven-plugin. IMHO they are probably a lot
True, but the Java version running the slave (and hence Maven) is not easily controllable on a project-by-project basis to begin with: a serious Jenkins installation could have hundreds of jobs running on various nodes, with different jobs being targeted to different Java baseline versions. An instance admin ought to be able to decide to use (say) 7u7 unconditionally for all slave.jar, while a job admin ought to be able to use 6u10 or whatever they like just by picking the right value from the JDK pulldown.
