Thanks for the info.
We told our clients already for more than a year to update to the latest OpenWebstart and use update checks.
Unfortunately they don't listen to us and even some still use Oracle JDK8 and Oracle webstart
From your snippet, how das Install4JUtils know to look into the OpenWebstart stage1 log? Client machines could have multiple applications installed with Install4J, no?
We have some clients which still use an older Version of OpenWebstart (prior 1.9.1) which had issues with JDK21. Next year we ...
is it possible to determine the OpenWebstart version from the Java program which is launched by OpenWebstart?
We can see that there are a few environment variable which start with "ows." but I can't see any that show the OpenWebstart version.
The problem was that my Intel based Mac picked up the parameters from <resources arch="x86"> even though it is a "x86_64" architecture. Here is a snippet of the NOT working file.
When testing with Oracle JDK17, I realized that it did not work either and took a deeper look when comparing the 2 logfiles. I realized that not all "-add-exports=..." that we had defined showed up when using Mac, but they did with Windows.
We have an issue using latest OpenWebstart version on Mac OSX with Temurin17. For our Swing Look&Feel we add multiple "--add-exports" and "--add-reads" to the JNLP file which is working fine with Windows and Temurin17. But on Mac OSX it looks like that Temurin17 is not using those parameters.