Released: Dec 15, 2023

2023 R2 での更新項目

機能

• New Variable to Generate Log on Specific Condition - In previous releases, InstallAnywhere generated a log file on all conditions during installation and uninstallation. This release introduces a new variable named-$IA_CONDITIONAL_LOG$ in the InstallAnywhere variables list to generate a log file on a specified condition during installation or uninstallation. This variable is recommended for use only in the Pre-Install or Pre-Uninstall view on the Sequence page.
  • The $IA_CONDITIONAL_LOG$ variable can be set to the following values using the 'Set InstallAnywhere Variable - Single Variable or Set InstallAnywhere Variable - Multiple Variable' action in the Pre-Install or Pre-Uninstall view on the Sequence page to generate a log file on a specific condition:
    • SUCCESS.
    • WARNING.
    • ERROR.
    • INCOMPLETE.
    • SKIPPED.
    • CANCELLED.

不具合の修正

• A new JRE patch enhancement in Java 11.0.20 caused the installer to abort with an error message: Invalid CEN header (invalid zip64 extra data field size) ZipException.
• On the Windows platform, launching the installer with the Regional Format setting set to French and the Show 24 hour date format in logs setting set to Yes led to a failure with an error dialog NullPointerException.
• While connecting to the multiple database (DB) systems, the custom action failed with an error indicating custom action's dependencies were not found at runtime due to insufficient support for the multiple service provider configurations.
• The Shortcut destination for all users changed into the user directory due to modification in the Program group name.
• Installer with a size larger than 2 gigabytes (GB) failed to install on the Windows platform.
• Installer displayed an Incorrect and static size of disk when the Expand Archive action was used to add payload.
• InstallAnywhere variable usage as part of a LaunchAnywhere's Name property led the installed LaunchAnywhere to be non-functional when installed on the macOS platform.
• Populating the Selected Archive and Existing Archive options of the Expand Archive action led to an excessive increase in the required disk space.
• The Merge module failed to install with Java 17.0.8.
• Installer installation failed to eliminate empty spaces at the beginning and end of user input fields.
• Documentation failed to mention that JAR files are no longer distributed with the InstallAnywhere installer.
• Documentation failed to describe the response file creation, when path and file name are not specified while using the -r command-line switch.
• Password appeared in the debug log even when the variable was configured to be excluded from logs.
• When the $USER_INSTALL_DIR$ is located on a mounted file system, if a directory in the path of the mount point contains a blank space in its name, the disk space check that occurs during the Pre-Install sequence is incorrectly returning the free disk space information for the root partition.
• Updating the installer that loads the previous version's installer properties failed to install all uninstaller resources and generated errors.
• The classpath was not honored and the Installer failed to load BC-FIPS as the security provider during run time.
• The installer title image icon failed to display while developing a project on the Windows platform and building on the Linux platform.
• Installing the uninstaller led to a failure during an upgrade.
• InstallAnywhere executed a malicious executable which was renamed to java.exe and available in the Java installation location with the same privilege as when run as the elevated user.