[
https://issues.apache.org/jira/browse/BUILDS-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238349#comment-14238349
]
Andrew Bayer commented on BUILDS-38:
------------------------------------
So in general, I'd advise against using the /home/jenkins/tools/java/* JDKs if
you can avoid it - as I mentioned in the thread when I was misunderstanding
exactly the question, we're moving away from manually installing the JDKs
everywhere and leaning towards using Jenkins' ability to auto-install JDKs from
Oracle onto the slaves when you select it from the JDK dropdown. With the Tool
Environment plugin, you can still use those auto-installed JDKs in
non-Ant/Maven build steps by having it export the path to the JDK into the
shell step environment as well.
I've added "latest1.6", "latest1.7", and "latest1.8" JDKs to the Jenkins
dropdown - if those get stale, someone will need to open a JIRA to let us know
so we can bump them, but the JDK choices in the dropdown will stay the same.
> java/latest symlinks point to non-latest versions
> -------------------------------------------------
>
> Key: BUILDS-38
> URL: https://issues.apache.org/jira/browse/BUILDS-38
> Project: Infra Build Platform
> Issue Type: Bug
> Environment: jenkins on the ubuntu hadoop build machines
> Reporter: Steve Loughran
>
> the various java/latest symlinks do not point to the latest versions of java;
> attempting to use them means you end up with outdated versions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
