install4j

What's new in this version:

New features:
- Launchers: Added support for creating an AOT cache on the first run with Java 25+, which can significantly reduce the startup time
- Added YAML actions for reading, counting, modifying, and writing YAML files
- Added SBOM generation for the install4j runtime components, with optional augmentation of existing SBOMs

Fixed:
- Fixed rollback processing for elevated action lists
- The installer hung when the elevated helper process died while an action was waiting for a response
- Proxy credentials entered in the unelevated process were not reused by the elevated helper and the user was asked again
- Improved robustness of uninstallation metadata
- If the default uninstall mode was set to "never uninstall", directories were still removed by the uninstaller
- When reading text files, two NUL bytes were injected into empty files and one NUL byte was appended to one-byte files
- "Execute SQL script" action: The action executed an unterminated statement prematurely when a line contained a delimiter and the statement continued on the next line
- "Add a startup executable" action: A NullPointerException was thrown when no arguments were configured on Linux
- "Modify a text file" action: The action missed matches when the search value had a repeated prefix, and failed with an exception for an empty search value
- "Modify an environment variable on Windows" action: The uninstallation corrupted the environment variable when a prepended value was removed after the variable had been changed by a third party
- "Add a Windows firewall rule" action and Win21Firewall.​addRule(​...​): Improved profile selection handling
- "Create a file association" and "Register a URL handler" actions: On Linux, when reinstalling or updating an installation, a duplicate MimeType entry was added to the desktop file if the association was already registered
- "Add VM options" action: The action did not work for application bundles that contained ".​app" in the middle of their name, and an existing VM option could be replaced by an unrelated option that started with the same characters
- For launcher arguments and VM parameters, the fallback value in installer variables of the form ${installer:​myVar?:​fallback value} was not used if the installer variable was not set
- Unix launchers: VM options files with Windows line endings prevented the application from starting
- Unix launchers: If stdout redirection was enabled but stderr redirection was disabled, the launcher failed to start. Also, redirecting stdout and stderr to the same file with different redirection modes is now rejected with an error message
- Unix services: For services running longer than the temp-cleaning interval of the system, the service id file could be deleted, causing wrong status reports and duplicate service starts
- macOS: Improved administrator detection
- macOS: Fixed several problems in the native libraries, including broken Unicode handling, a non-functional native file chooser, and truncated long paths in JRE archives
- The system property install4j.​disableMacosProcessCheck was inverted
- The shutdown lock for update installations could be released by the garbage collector while the application was still running
- Background updates: Fixed several problems with scheduled and concurrently running update operations, including updates started by a service on macOS
- Update descriptors without a "singleBundle" attribute incorrectly reported single bundle archives for archives
- External launchers in directory entries of the distribution tree were not made executable, and custom file options of the directory entry were not applied to them
- Command line compiler variable definitions with a media file or platform scope did not work for variables that were not defined in the project
- Compiler variable fallbacks with the Elvis operator did not work for environment variables and file contents, and a fallback in ${compiler:​sys.​mediaName?:​...​} was not used outside a media-file specific context
- Separator conversion of variable values corrupted Windows drive letters and URLs, and backslashes were lost if a compiler variable with a Windows path was used in a string array installer variable
- Media-file overrides now preserve the hidden status of compiler variables
- Generated JRE bundles: If a project was saved by an older version with an Alpine Linux x64 JRE bundle, an ARM JRE was bundled instead
- MSI media files: Improved handling of existing digital signatures during signing
- RPM media files: Non-ASCII characters in package descriptions and file names were corrupted
- RPM media files: The build now fails with a clear error message if files larger than 2 GB are included instead of creating a corrupted RPM
- macOS DMG media files: File names with many accented characters close to the maximum name length corrupted the DMG catalog
- MSIX media files: The package identity name could contain an underscore, producing a package that is rejected by Windows. Also, clearing the minimum or maximum Windows version produced a package with empty version attributes that Windows refuses to install
- Actions that were only contained in action groups of action lists were removed by runtime shrinking and were not rolled back
- Corrected elevation handling for actions in nested form component groups
- "Combo box" form component: When the disabled background color was set via the widget style, the text in the disabled state was painted with the same color, making it invisible
- API: Calling FormEnvironment.​getFormComponents(​Class) or getFirstFormComponent(​Class) at design time could throw an exception or return no components if form component groups were present
- Custom localization files could not be loaded when a line started with an equal sign, and Windows paths in them were corrupted by incorrect unescaping
- Improved detection of user-specific installation paths
- If saving a project failed midway, for example, when the disk was full, the project file was corrupted
- The "Preserve symbolic links" setting in the "File → File Options" view was not saved to the project file
- After a failed build in the IDE, scripts of the failed build could be included in the next build
- Fixed numerous problems in the install4j IDE
- Fixed numerous robustness problems in native code