Thanks Uwe, this is very helpful!
2017-06-29 0:01 GMT+02:00 Uwe Schindler :
> Hi,
>
> Instead of native Maven build jobs, the easy workaround is:
>
> - Use a standard Freestyle Job
> - Check the right JDK version
> - Use the "Tool Environment" plugin and select correct Maven version, e.g.
> MAVEN
Hi,
Instead of native Maven build jobs, the easy workaround is:
- Use a standard Freestyle Job
- Check the right JDK version
- Use the "Tool Environment" plugin and select correct Maven version, e.g.
MAVEN_3_5_0_HOME
- Enter the Maven execution into the shell command line and use the "Tool
Envi
I think it depends upon your job type, as Gavin wrote: "in terms of Maven
jobs for JDK 7"
On Wed, Jun 28, 2017 at 10:01 AM, Lukasz Lenart
wrote:
> Hi,
>
> How to understand that? It won't be possible to run a job using JDK7
> anymore, right? Even if I selected such JDK in my build, Jenkins won't
Hi,
How to understand that? It won't be possible to run a job using JDK7
anymore, right? Even if I selected such JDK in my build, Jenkins won't
run it, is that true?
We cannot run this build [1] anymore as JDK6 isn't support by the
slaves [2] - will it be the same?
[1] https://builds.apache.org/
