Re: Jenkins and Maven builds using a different JDK

2017-06-30 Thread sebb
On 30 June 2017 at 00:49, sebb wrote: > On 29 June 2017 at 15:51, Oleg Kalnichevski wrote: >> On Thu, 2017-06-29 at 13:42 +0100, sebb wrote: >>> It looks as though the Maven toolchains.xml file has been set up for >>> most of the JDKs on Jenkins. >>> >> >> ... >> >>> >>> Ideally this should be se

Re: Jenkins and Maven builds using a different JDK

2017-06-29 Thread sebb
On 29 June 2017 at 15:51, Oleg Kalnichevski wrote: > On Thu, 2017-06-29 at 13:42 +0100, sebb wrote: >> It looks as though the Maven toolchains.xml file has been set up for >> most of the JDKs on Jenkins. >> > > ... > >> >> Ideally this should be set up in the parent POM, but for testing it >> woul

Re: Jenkins and Maven builds using a different JDK

2017-06-29 Thread Oleg Kalnichevski
On Thu, 2017-06-29 at 13:42 +0100, sebb wrote: > It looks as though the Maven toolchains.xml file has been set up for > most of the JDKs on Jenkins. > ... > > Ideally this should be set up in the parent POM, but for testing it > would make sense to temporarily add it to one of the components. >

Jenkins and Maven builds using a different JDK

2017-06-29 Thread sebb
It looks as though the Maven toolchains.xml file has been set up for most of the JDKs on Jenkins. This means it should be possible to run Maven using whatever JDK version Jenkins wants - which can change - but still compile/test using a possibly different fixed JDK version. One way to to do this