[
https://issues.apache.org/jira/browse/AMBARI-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Sposetti updated AMBARI-4212:
----------------------------------
Description:
Ambari supports JDK 1.6 and 1.7, as well as using an existing/custom JDK
(already installed by user).
Ambari should handle setup of JDK more cleanly, which also includes matching
JCE setup version with JDK version and make it easier to adjust JDK
post-install.
was:
Ambari supports JDK 1.6 and 1.7, as well as using an existing/custom JDK
(already installed by user).
Ambari should handle setup of JDK more cleanly, which also includes matching
JCE setup version with JDK version.
The following document describes adjusts to ambari-server setup to make JDK
selection more clear, handle matching JCE with JDK version, and handle
ambari-server JDK change post install.
https://docs.google.com/a/hortonworks.com/document/d/1g1VOQOuK6NLwK1vc1ScyfcKgOwx6p6CSpJw49ObGqTk/edit
> Ambari should handle available JDK 6 vs 7 correctly
> ---------------------------------------------------
>
> Key: AMBARI-4212
> URL: https://issues.apache.org/jira/browse/AMBARI-4212
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Vitaly Brodetskyi
> Fix For: 1.5.0
>
> Attachments: AMBARI-4212.patch
>
>
> Ambari supports JDK 1.6 and 1.7, as well as using an existing/custom JDK
> (already installed by user).
> Ambari should handle setup of JDK more cleanly, which also includes matching
> JCE setup version with JDK version and make it easier to adjust JDK
> post-install.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
