We are committed to providing good solid support for all Java versions our customers run The Muse Platform on. However, as new versions of Java, web browsers, and in general software technologies, are released, it is becoming more and more difficult to provide support for old Muse versions running on old Java versions which are out of support and lack new important features and security related standards.
More exactly, starting with July 1st 2017 we are no longer supporting the following Muse versions which run only with Java 6:
- Muse 2.5, released on 2010-10-07
- Muse 2.6, released on 2012-06-26
Java 6, end of its support life in February 2013. [https://en.wikipedia.org/wiki/Java_version_history#Java_SE_6]
Java 9 is now expected to be released on 2017-07-27.[http://openjdk.java.net/projects/jdk9/]
Technically, starting July 1st 2017, Muse Building Environment will no longer produce binary code compatible with Java 6. We will start compiling the entire Muse Platform including Muse Source Packages for Java Virtual Machine 8, hence they will no longer run under Java Virtual Machine 6.
Note that Muse versions 2.5 and 2.6 are not running with newer Java 8 versions.
Your 2.5 and 2.6 Muse installations will continue to function after July 1st 2017 according to your Licensing Agreement, however they will no longer be able to run automatic or manual updates that we provide via Muse Source Factory. If by July 1st 2017 you still run one of the old Muse versions – 2.5 or 2.6 – you must turn OFF the Muse Control Center task doing the automatic updates of the Muse Source Packages.
Please address your concerns with our Technical Support Department at email@example.com or any questions you may have regarding this change.
We recommend that you start upgrading your customer installations to using Muse version 2.7 and the latest Oracle Java 8 build. Note that your existing Muse Applications user (web) interface should continue to run or require minimal compatibility fixes, under Muse version 2.7. If very particular cases arise we can create custom patches to accommodate this.
We make the same suggestion of contacting our Technical Support Department at firstname.lastname@example.org for any questions and help regarding this upgrade.