Softpedia >Windows >Authoring Tools >Setup creators >exe4j >  Changelog

exe4j Changelog

What's new in exe4j 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 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 8.0.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 7.0.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 6.0.2 (Jan 9, 2020)

  • New features:
  • Support for OpenJ9 VMs
  • -J-splash:none can be passed as an argument to disable the splash screen
  • Bugs fixed:
  • If the environment variable _JAVA_OPTIONS was set, the version check for Java 9+ did not work on Windows
  • The Java version check did not work for some newer OpenJDKs

New in exe4j 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 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

New in exe4j 5.0.1 (Feb 9, 2015)

  • Bugs fixed:
  • Fixed crash on startup for very large classpaths
  • ant.jar file was missing in the distribution since 5.0
  • License keys for install4j 6.x were not accepted in the wizard

New in exe4j 5.0 (Feb 9, 2015)

  • New features:
  • Generated launchers no longer poll the file system for the internal single instance and splash screen communications
  • Splash screen API now works for the Java splash screen as well
  • Added "/run" and "/run-redirect" parameter for services to start a service in command line mode from a terminal
  • Support DPI scaling for with a setting on the "Executable info->Windows manifest options step" of the launcher wizard
  • Native file choosers and alerts in the exe4j wizard
  • Generated launchers now require at least Java 6, the exe4j IDE now requires at least Java 7

New in exe4j 4.6 (Jun 9, 2014)

  • exe4j now uses wide characters internally, fixing several problems with characters in directory names from outside the default code page
  • Expand launcher variables and environment variables in working directory
  • exe4j wizard can now run with Java 8

New in exe4j 4.5.1 (Jan 16, 2013)

  • The exe4j wizard now uses the native look and feel

New in exe4j 4.5.1 (Nov 28, 2012)

  • Fixed problem with Windows 8 certification
  • Do not force Java 6 locale behavior for Java 7
  • exe4j license dialog showed invalid evaluation option

New in exe4j 4.5 (Sep 21, 2012)

  • New features:
  • Generated executables now pass Windows 8 certification
  • Bugs fixed:
  • JAR in EXE service did not delete all temp files
  • Unbalanced quotes for arguments were not handled correctly
  • Fixed a race condition with the exe4j splash screen

New in exe4j 4.4.6 (Jul 2, 2012)

  • Bugs fixed:
  • Several command line options were broken (regression in 4.4.5)
  • Javadoc formatting of the API documentation was broken (regression in 4.4.5)

New in exe4j 4.4.5 (Jun 18, 2012)

  • New features:
  • Java 7 can now be used to run the exe4j wizard and the exe4j command line compiler
  • Bugs fixed:
  • Temporary directory creation is now more robust
  • Remove temporary files if no JRE can be found

New in exe4j 4.4.4 (Jun 18, 2012)

  • Fixed locale regressions in 4.4.3

New in exe4j 4.4.3 (Jun 18, 2012)

  • New features:
  • Add a compatibility manifest for Windows 7 to generated executables
  • Bugs fixed:
  • Service shutdown did not work correctly when user code redirected System.in
  • Single instance mode for launchers was broken if there were spaces in the name of the executable
  • Some operations in SWT applications could be slow due an application manifest entry

New in exe4j 4.4.2 (Jun 18, 2012)

  • New features:
  • Make executable name available for JVM discovery, for example in VisualVM
  • Bugs fixed:
  • Language selection was ignored, the language for error messages was always English
  • In the fixed VM parameters, a "\n" was replaced with a newline character

New in exe4j 4.4.1 (Oct 23, 2010)

  • New features:
  • Allow a * placeholder in classpath archive entries to support frequently changing version numbers of JAR files like in maven projects
  • Bugs fixed:
  • Service arguments embedded in the registered binary path did not work correctly
  • Fixed a deadlock for service launchers