Page History

...

• JobScheduler can be operated with a Java Runtime Environment (JRE) and Java Development Kit (JDK).
• Java releases provided by Oracle® (https://www.oracle.com/java/technologies/) and by OpenJDK® (https://adoptium.net/) are supported. 
  
  • Java LTS releases are considered for Supported Compatibility ¹⁾, Java feature releases might be considered for Reported Compatibility ²⁾ by the JobScheduler community.
  • Should the OpenJDK® project at a later point in time provide Java LTS releases and respective Java updates then SOS will check to integrate into the life cycle.
• Java distributions of other vendors are not considered for Supported Compatibility ¹⁾, however, Reported Compatibility ²⁾ might be indicated by the JobScheduler users community or by SOS. 
• Customers can ask SOS to perform compatibility testing as a service for Java distributions of other vendors and for Java feature releases.

...

• Since Java 9 Oracle® changed the JVM life cycle:
  • New Java feature releases ship every 6 months, Java LTS releases ship approx. every 2 years, see the Java SE Support Roadmap (https://www.oracle.com/java/technologies/java-se-support-roadmap.html).
  • Public maintenance for Java feature releases is restricted to 6 months. Users can opt for a support contract with Oracle® to prolong maintenance for Java.
  • Java releases do not follow semantic versioning.
• These changes affect JobScheduler releases as follows:
  • We SOS cannot know in advance if new Java releases will or will not be compatible with existing JobScheduler releases. Compatibility testing requires substantial effort and is partly performed by the JobScheduler community, see below explanations on Supported Compatibility ¹⁾ and Reported Compatibility ²⁾.
  • JobScheduler Agents are available for a larger number of platforms, including AIX®, HP-UX® etc. Such platforms tend to implement new JVM releases with some substantial delay. 
• SOS Release Policies
  
  • All JobScheduler components (Controller/Master, Agent, JOC Cockpit) are built with the same Java release.
  • JobScheduler components are not built with the newest Java release but with the oldest compatible Java release, e.g. JobScheduler 1.12 and 2.0 are built with Java 1.8.
  • We try to consider SOS considers compatibility with newer Java feature releases, e.g. a JobScheduler Master 1.12.2 is built with Java 1.8 and can be operated with Java 1.8, 9 and 10 that are supported Java releases at the time of public availability of the JobScheduler Master. We do SOS does not guarantee compatibility with upcoming Java feature releases.
  • For use of JobScheduler Long Term Support releases we encourage SOS encourages users to opt for a Java LTS release that provides maintenance for the same duration as JobScheduler LTS maintenance, see How long will you support the different versions of JobScheduler and YADE?
    • We strive SOS strives for compatibility of JobScheduler LTS releases with newer Java LTS releases, however, we do SOS does not check compatibility with individual Java feature release.
    • We SOS will not modify JobScheduler LTS releases to be built with newer Java versions. We  SOS will check to modify existing code to be compatible with the Java LTS release that has originally been used and with newer Java LTS releases, however, feasibility cannot be guaranteed as this depends on the extent of compatibility gaps between Java releases. 
    • For JobScheduler release 1.12 Java 1.8 is used for the build environment and  Java 9,10, 11 can be used at run-time.
  • JobScheduler is used with a number of DBMS product products and vendor specific JDBC Drivers. Use of a specific DBMS and JDBC Driver limits the compatibility with specific Java releases. Check the DBMS Compatibility Matrix from the Which Database Management Systems are supported by JobScheduler? article.

...

...