We are in a similar position and another option (while exploring migration away from the Maven type) is that, while Maven itself must run JDK 7+, it can fork to a lower JDK. This forking is handled by Jenkins automatically and coiuld serve as a stopgap.
On Tuesday, November 24, 2015 at 4:06:32 AM UTC-5, guido.wojke wrote: > > Hello everybody, > > due to a JDK 6 dependency on our build system we can't upgrade to Jenkins > 1.625.2 which forces a JDK 7 or higher to build maven job type. > We use the LTS 1.609.3 with the security workaround desribed here: > > https://jenkins-ci.org/content/mitigating-unauthenticated-remote-code-execution-0-day-jenkins-cli > > Is it possible to provide a LTS Version 1.609.4 with the security > update(s) provided in > the 1.625.1->1.625.2 update (f.e. the Important security fixes)? > > Best regards, > Guido > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/6fd2c69f-76a9-4019-a2c9-883579a9e375%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
