What's new in exe4j Portable 9.0
Jan 17, 2023
- New features:
- Support for creating ARM64 executables on the "Executable info->Architecture" step
- Optionally global single instance mode on the new "Executable info->Single instance mode" step
- The per-user single instance mode now optionally covers all active sessions
- Support for finding Microsoft, Zulu and Temurin JRE installations
- Show number of configured version-specific VM parameter entries in the "Java invocation" step
- Bugs fixed:
- Startup notifications that occurred before a listener was registered were not delivered in order
- If dark mode was used in macOS 13 (Ventura), the exe4j wizard would hang on startup
New in exe4j Portable 8.0.1 (Feb 18, 2022)
- New features:
- Support dark mode for the exe4j wizard
- Bugs fixed:
- Regression in exe4j 8.0: bin/ant.jar was missing
- Changed the way command line parameters are split to behave like java.exe
- Fixed broken Java version check in some situations
New in exe4j Portable 8.0 (Mar 11, 2021)
- New features:
- Added support for non-OpenJDK Java launchers
- Added a --fail-on-warning command line option for the compiler as well as corresponding properties for Gradle and Ant tasks
- 64-bit install4j launchers now prefer the server JVM on Windows. This fixes problems with recent AdoptOpenJDK Java 11 releases that contain a client VM.
- Using ~ for the home directory is now supported for the redirection files
- The minimum runtime Java version is now 1.8, the exe4j compiler and wizard need a Java 11 JRE
- Bugs fixed:
- Could not use absolute locations for the JRE search sequence when the build was not performed on Windows
- An empty JRE search sequence was reverted to the default after opening the project again
New in exe4j Portable 7.0 (Jan 9, 2020)
- New features:
- Support for version ranges in version-specific VM options for launchers
- Less verbose and more human-readable project file format that does not write default settings
- Bugs fixed:
- For OSGI applications, the method to hide the splash screen could not work due to classloader issues
- Using archives in class and resource paths with a wildcard in the file name did not work if the path was absolute
New in exe4j Portable 6.0.1 (Aug 26, 2018)
- New features:
- Removed empty class path warning
- Uncaught exceptions in exe4j wizard are now written to %TEMP%exe4j_error.log
- Support for running the exe4j wizard and its command line tools with Java 10 and Java 11
- Bugs fixed:
- Regression in exe4j 6.0: File and directory chooser buttons in class path configuration did not work anymore
New in exe4j Portable 6.0 (Jul 20, 2017)
- New features:
- Support for Java 9
- Executables can define a Java 9 module path in addition the the class path
- Support for the new multi-resolution features in Java 9, including multi-resolution splash screen support
- In the "Manifest options" step of the wizard, the new default "Java 9+" makes executables DPI aware if Java 9+ is used as a minimum version
- Added a "/restart" parameter for service executables
- Bugs fixed:
- If a JRE could not be loaded, more than one error message was shown in sequence
- Extra arguments were not passed correctly when starting a service executable with the /run parameter
- services installed with /install are now always non-interactive