www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: JDK names on Windows nodes & Jenkinsfile
Date Fri, 24 Mar 2017 14:57:02 GMT
On 24 March 2017 at 03:55, Hervé BOUTEMY <herve.boutemy@free.fr> wrote:
> Hi,
>
> It seems new JDKs were added to Windows nodes recently [1]: instead of "JDK
> 1.8 (unlimited security) 64-bit Windows only", we now have 2 options: "JDK
> 1.8.0_92 (unlimited security) 64-bit Windows only" and "JDK 1.8.0_121
> (unlimited security) 64-bit Windows only".
>
> Having new JDKs is great, but changing names is not great :)
>
> We're using Jenkinsfiles, with JDK names coded inside (we = Maven, but I
> suppose others do the same): until now, it was not fun to have a different JDK
> names for Linux and Windows nodes, but now having to follow very precise JDK
> name on Windows nodes is a new hurdle.
>
> Is it possible:
> 1. to have a JDK 8 alias on Windows that won't change over time, even if
> detailed version changes (like "JDK 1.x (latest)" on Ubuntu nodes"?
>
> 2. ideally to have the same name on Windows as on Linux nodes?
>

That would be great.

For example, define JAVA_1_n_HOME on each node to point to the latest
version of Java 1.n

This would be very helpful for Commons, as we use those names in
profiles that choose the compile and test Java versions.
I think some other projects use the same naming convention too.

> And of course, if I can help to make this happen, just tell me what to do.
>
> Regards,
>
> Hervé
>
> [1] https://cwiki.apache.org/confluence/pages/viewpreviousversions.action?
> pageId=65147537

Mime
View raw message