Frontpage Warning
With regard to the warning about Java 8 - I think we need to update it - from a security standpoint we can no longer be seen advocating the removal of Java 8 and reinstalling Java 7
Java 7
Auto-update Notice and End of Public Updates for Oracle JDK 7
As outlined in the Oracle JDK Support Roadmap, after April 2015, Oracle will not post further updates of Java SE 7 to its public download sites. Customers who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 7 or older versions can get long term support through Oracle Java SE Support. The process of migrating users from Java 7 to Java 8 through the auto update feature is expected to take place after the January 2015 CPU release.
Thus I believe the advice we need to be giving people is updating Tomcat to use Java 8
This means updating the Tomcat load script to find Java 8 either by updating the environment variable JAVA_HOME or updating the script
I recognise this typically would be an installer job not end user but that is not a good enough excuse to be seen recommending the use of a vulnerable product from a security standpoint. Noone is going to but JAVA SE support so we need to recommend Java 8 as a basic requirement as of now.
This will mean updating any installation documentation.
Re: Frontpage Warning
I recognize that jasperreports conflicts with this...
Openvpms.org can not support old versions. We probably should have produced a patch for 1.7 when this came up rather than holding it over to 8 - maybe we need to backport the jasper reports changes to 1.7 anyway to give those an option that dont want to migrate to 1.8.
Re: Frontpage Warning
At this stage there is no funding for a 1.7.2 release to support Java 8.
If enough users want it, then we can do it, but for now the focus is on 1.8 which support Java 8.
Re: Frontpage Warning
I have no problem with that line but we do need to make it clear that users running <1.8 at 1.8 release cannot be supported from the point of view of security vulnerabilities and the like.
Prior to that the warning needs to be changed to explain what running Java 1.7 might risk.