Timm

I have a JavaFx application, let's call it MyApp, with a bundled JRE (placed as a subfolder in the application directory) and the application starter MyApp.exe build with Launch4j. At startup the application checks if a new version is available and then auto loads changed jar files from an update server into a new folder (and copies all unchanged jar files from the previous version folder). The launch4j ini file is updated accordingy with the new directory as the classpath: -cp "libs/1.1.275/*" This...

I have a JavaFx application, let's call it MyApp, with a bundled JRE (placed as a subfolder in the application directory) and the application starter MyApp.exe build with Launch4j. At startup the application checks if a new version is available and then auto loads changed jar files from an update server into a new folder (and copies all unchanged jar files from the previous version folder). The launch4j ini file is updated accordingy with the new directory as the classpath: -cp "libs/1.1.275/*" This...

I have a JavaFx application, let's call it MyApp, with a bundled JRE (placed as a subfolder in the application directory) and the application starter MyApp.exe build with Launch4j. At startup the application checks if a new version is available and then auto loads changed jar files from an update server into a new folder (and copies all unchanged jar files from the previous version folder). The launch4j ini file is updated accordingy with the new directory as the classpath: -cp "libs/1.1.275/*" This...

I have a JavaFx application, let's call it MyApp, with a bundled JRE (placed as a subfolder in the application directory) and the application starter MyApp.exe build with Launch4j. At startup the application checks if a new version is available and then auto loads changed jar files from an update server into a new folder (and copies all unchanged jar files from the previous version folder). The launch4j ini file is updated accordingy with the new directory as the classpath: -cp "libs/1.1.275/*" This...

I have a JavaFx application, let's call it MyApp, with a bundled JRE (placed as a subfolder in the application directory) and the application starter MyApp.exe build with Launch4j. At startup the application checks if a new version is available and then auto loads changed jar files from an update server into a new folder (and copies all unchanged jar files from the previous version folder). The launch4j ini file is updated accordingy with the new directory as the classpath: -cp "libs/1.1.275/*" This...

I have a JavaFx application, let's call it MyApp, with a bundled JRE (placed as a subfolder in the application directory) and the application starter MyApp.exe build with Launch4j. At startup the application checks if a new version is available and then auto loads changed jar files from an update server into a new folder (and copies all unchanged files from the old version folder). The launch4j ini file is updated accordingy with the new directory as the classpath: -cp "libs/1.1.275/*" This is very...

I have a JavaFx application, let's call it MyApp, with a bundled JRE (placed as a subfolder in the application directory) and the application starter MyApp.exe build with Launch4j. At startup the application checks if a new version is available and then auto loads changed jar files from an update server into a new folder (and copies all unchanged files from the old version folder). The launch4j ini file is updated accordingy with the new directory as the classpath: -cp "libs/1.1.275/*" This is very...

I have a JavaFx application, let's call it MyApp, with a bundled JRE and the application starter MyApp.exe build with Launch4j. At startup the application checks if a new version is available and then auto updates its jar files into a new folder. The launch4j ini file is updated accordingy with the new directory as the classpath: -cp "libs/1.1.275/*" myapp.Main This is very simple to maintain, works great, and is rolled out to many user. The problem comes if I want to update the bundled JRE, because...