Our HR LTM base application users use the Landmark Rich Client to work in LTM. With recent updates to Java (1.8 update 171), one of the ciphers (3DES) used to download the application was disabled. In order for the Rich Client to download and install, we need to roll our Rich Client users back to java 1.8 update 161.
In order to not use an old version of java on all of these devices, we want to create an application package that contains the desktop Rich client (so no download is required). We cannot seem to get the packaging to work because the application automatically checks (the Landmark environment) for updates each time it is launched. We only upgrade Landmark twice a year and would create a new application package each upgrade - we are not looking to run an old version of the Rich Client against a newer Landmark version.
Have you figured out a way to stop the desktop installed Landmark Rich Client from checking for updates?
Do you have any other ideas on how to make this work with a static version of java - yet allowing the device to be upgraded to the newest version of Java.
The use of Java (and what is supported by Oracle) is really changing, so we're TRYING to get ahead of the ball with the Rich client. There is no mention of Java 11 in the Compatibility matrix and that worries me a bit too.
