What's new in JLaunch 1.4
Aug 16, 2012
- JLaunch exe file command line parameters are passed through to the Java application (on the java command line) as application parameters, if there are any.
- JLaunch exe was altered to read a new configuration file parameter "java.jar" which can specify an executable Jar file rather than a main java class name.
- Set up an exclusive OR arrangement with java class name, and jar file name.
- This change has also been implemented in the Configurator tool.
New in JLaunch 1.3a (Aug 16, 2012)
- Increased the memory length for configuration file key/value pairs, as very large classpaths were failing.
New in JLaunch 1.3 (Aug 16, 2012)
- Fixed bug in Configurator with the resetting of the Java Application Parameter field.
- Added a 'current directory' concept to the Configurators "Mandatory" tab. By clicking on the ellipses button (...) you can navigate to a directory of your choice and configure/create CFG files in there.
- Added a new tab to the Configurator tool, called "Executable" to allow creation of JLaunch executable programs (icons) for configured applications. The user selects the icon of choice, and an appropriately named EXE is created.
- Added an option to the "Launcher" tab called "Show Java Console Window". When selected, JLaunch will execute Java with the DOS console window visible. This is suitable for debugging your application startup, and viewing console output.
New in JLaunch 1.2 a/b/c/d (Aug 16, 2012)
- Fixed a bug with the current directory path changing after a Java VM has been selected by the user.
- Fixed bug with process being left behind if splash screen not in use.
- Fixed splash screen timeout discrepancies.
- Fixed classpath truncation issues.
- Fixed bug with startup if configuration file is read only.
New in JLaunch 1.2 (Aug 16, 2012)
- Automatic JRE/JDK download (via an Internet Explorer browser launch) for users where a JRE/JDK version is not found in the Windows Registry.
- Java Version Only setting. Can be set to Yes if the Java application requires a specific Java Runtime version for execution. Otherwise, Java versions and above can be used for launching.
- Java Param setting. Allows Java applications to specify command line arguments passed directly into the Java program.
- Seperated Shareware Lock and Application Lock code for source code distribution.
New in JLaunch 1.1 (Aug 16, 2012)
- Bug fix for java runtime setting. If the javaw.exe location stored in the configuration file goes missing, JLaunch will now attempt to relocate the runtime.
- Now searches for a valid JRE version, and upon failing, searches for a JDK version.
- This may occur if developers run JLaunch applications.
- JRE Only and JDK Only settings. Allows software to look for only installations of a given type if required.
- Debug Option. Allows the launcher to pop up debug messages, as it steps through the process of launching an application. Useful for identifying typos in an application's configuration settings or classpath settings.
New in JLaunch 1.0 (Aug 16, 2012)
- Initial product development