On Sat, Oct 29, 2016 at 6:33 AM, Arnaud Héritier <aherit...@gmail.com> wrote: > The problem is that when a user have a large number of maven jobs running on > old JDKs, these are often legacy projects where the maintenance cost must be > 0. The problem is that using toolchains requires to update you maven project
I feel like I am repeating myself, but: if you run a Maven project configured to use an older JDK than what Jenkins (master + agent) supports, the plugin *already* switches your build to use external tools from that JDK (while Maven itself runs in the same JRE as the node). This happens using properties defined for common mojos; there is no need to switch to toolchains or edit your POM. Now this is not going to handle exotic plugins or POMs with weird configuration, but it should handle the vanilla cases. This has been true for a long time, since we dropped JDK 5 support IIRC. -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2aNotGx8soW8-QXHTF3pUQLZNXFELghYkiRpMUirmoQw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
