[Amazon Linux AMI](https://aws.amazon.com/cn/amazon-linux-ami/2016.09-release-notes/) is another RedHat-like os image, openjdk-7 was shipped in that image but we want more choices or jdk 8. i'd been tested ok for oracle jdk installation on a 't2.micro' instance.
We are having issues on reboot of boxes. It tries to download to tmp even though already installed, which would be fine,
but the version is no longer available.
This results in curl downloading something to tmp every time puppet runs, which eventualy fills up tmp :(
* Allow targeting specific major/minor Oracle JDK versions
Expose two new parameters 'version_major' and 'version_minor' to
allow users targeting specific Oracle JDK versions.
Signed-off-by: Gregor Zurowski <gregor@zurowski.org>
* Fix lint validation issues
Signed-off-by: Gregor Zurowski <gregor@zurowski.org>
This commit changes the way the JAVA_HOME variable is added to
/etc/environment from using a file resource to using an exec
resource. This way we can avoid resource conflicts with the
file.
Signed-off-by: Nate Potter <ntpttr@gmail.com>
New versions of oracle java 8 >= 100 have an updated naming scheme. These
test cases validate the new conditional logic around this for Debian and
derivatives.
The previous make-jpkg from java-package_0.50 doesn't support building java
versions with three digits in the release number. Therefore it has been
necessary to upgrade java-packaages to the newer 0.53 version.
Building oracle packages using the java-package tools 0.53 results in package
with a new naming scheme as compared to 0.50. In particular where the packages
were previously named oracle-j2re1.8 they are now named oracle-java8-jre, while
oracle-j2dk1.8 has become oracle-java8-jdk. The alternatives naming has also
changed.
We also need to handle the system architecture naming on debian systems where
Debian names it's 64bit architecture 'amd64' and Oracle use 'x64'. This results
in the java_home path using x64 rather than amd64. We need to handle this
variation while also accommodating all architectures, and only for the recent
packages.
Given this has only been tested on Ubuntu, and the make-jpkg tooling is managed
in the Debian flavour, the changes are only applied to that code branch.
Jinn Koriech & Doug Neal
