Skip to content

Update Java JDK from 8u141 to 9.0.1 #531

Merged
merged 1 commit into from
Nov 27, 2017
Merged

Commits on Nov 15, 2017

  1. java: Update version from 8u141 to 9.0.1

    Java 9 was released in September 2017. It supports HiDPI displays [1].
    Most changes are detaled in the *Java Platform, Standard Edition Oracle
    JDK 9 Migration Guide* [2].
    
    Switch to the new version scheme.
    
    > ### New Version-String Scheme ###
    >
    > JDK 9 provides a new simplified version-string format. If your code
    > relies on the version-string format to distinguish major, minor,
    > security, and patch update releases, then you may need to update it.
    >
    > The format of the new version-string is:
    >
    > $MAJOR.$MINOR.$SECURITY.$PATCH
    >
    > For example, under the old scheme, the Java 9u5 security release would
    > have the version string 1.9.0_5-b20.
    >
    > Under the new scheme, the short version of the same release is 9.0.1,
    > and the long version is 9.0.1+20.
    >
    > This change affects java -version and related system properties, such
    > as java.runtime.version, java.vm.version, java.specification.version,
    > and java.vm.specification.version.
    >
    > A simple Java API to parse, validate, and compare version strings has
    > been added. See java.lang.Runtime.Version.
    >
    > See Version String Format in Java Platform, Standard Edition
    > Installation Guide, and JEP 223: New Version-String Scheme.
    
    Additionally, JCE Jurisdiction Policy File default is now unlimited,
    meaning the installation can be removed from the bee file.
    
    > ### JCE Jurisdiction Policy File Default is Unlimited ###
    >
    > If your application previously required the Java Cryptography
    > Extension (JCE) Unlimited Strength Jurisdiction Policy Files, then you
    > no longer need to download or install them. They are included in the
    > JDK and are activated by default.
    >
    > If your country or usage requires a more restrictive policy, the
    > limited Java cryptographic policy files are still available.
    >
    > If you have requirements that are not met by either of the policy
    > files provided by default, then you can customize these policy files
    > to meet your needs.
    >
    > See the `crypto.policy` Security property in the
    > `<java-home>/conf/security/java.security` file, or Cryptographic
    > Strength Configuration in the Java Platform, Standard Edition Security
    > Developer's Guide.
    >
    > You are advised to consult your export/import control counsel or
    > attorney to determine the exact requirements.
    
    [1] http://openjdk.java.net/jeps/263
    [2] https://docs.oracle.com/javase/9/migrate/
    pmenzel committed Nov 15, 2017
    Configuration menu
    Copy the full SHA
    0b93a5f View commit details
    Browse the repository at this point in the history