Launch4j is a cross-platform tool for wrapping Java applications distributed as jars in Windows native executables. The executable can be configured to search for a certain JRE version or use a bundled one, and it's possible to set runtime options, like the initial/max heap size. The wrapper also provides better user experience through an application icon, a native pre-JRE splash screen, a custom process name, and a Java download page in case the appropriate JRE cannot be found. The increase in size of the application is small.
|Tags||Software Development Build Tools Software Distribution Tools|
|Licenses||MIT/X BSD Revised|
|Operating Systems||POSIX Linux Windows Windows Mac OS X|
Release Notes: Support for 64-bit Windows, 64-bit JRE, and IBM JRE was added. A Java runtime preference option was introduced. It is now possible to set the initial process priority and allow running only a single instance of the application. Dynamic initial and maximum heap sizes were added. The error reporting was redesigned and now supports custom messages. The runtime logging produces more detailed output. Various bugs were fixed, and the license was changed to a less restrictive one.
Release Notes: The configuration file format and embedded Ant configuration have been improved. It's now possible to launch executable jars, regular jars, and class files. Dynamic classpath resolution with environment variable references and wildcards has been added. An option to set environment variables before launching the application has been added. New commandline switches change the compiled options. The debug mode is easier to use. Xp-style manifests are supported. There is now an option to disable the use of private JREs.
Release Notes: The Java download site has changed to http://java.com/download. It's now possible to use absolute and relative paths to specify the embedded JRE.
Release Notes: A bug where only the first wrapper instance had a custom process name was fixed.
Release Notes: An Ant task bug was fixed, some relative jar paths were handled incorrectly. The jar argument size limit is now 16KB. The environment variable size limit was raised to 32KB. It's possible to concatenate multiple environment variables in one property. A working directory property was added.