Hello list, I try to get a fix for https://issues.jenkins-ci.org/browse/JENKINS-40990 (the new remoting in jenkins 2.32.1 causes maven builds with older jdk to fail).
The mechanism to switch the jdk used to run maven to the platform jdk if a " UnsupportedClassVersionError" is caught does not kick in because this exception is not carried as cause any more and thus this situation is not detected. (affected class hudson.maven.AbstractMavenProcessFactory 298ff). My main requirements are: - must be able to run jdk 5 & 6 builds without a change in the projects pom - should not need to add hard coded path pointing to the jenkins auto-installed jdks anywhere - should not rely on the platform jdk to be the one to use I think about a new option for the maven builds to allow to set the maven.compiler.executable and related variables based on a independent jdk selection. So one could choose to run maven with "jdk1.8.0" but to point the maven compiler etc. to "jdk1.5.0". The disadvantage of this is that the job configuration needs to be updated for every affected job, but we would gain control over the fallback jdk that is used. With the resent security fixes and the upcoming switch to java8 only this becomes critical to me since it blocks me from updating to the latest jenkins. Thoughts? Kind Regards, Andreas. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/15492026-0483-4ee1-8a28-cce67d668976%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
