install4j 11.0.2

What's new in this version:

New features:
- Added a compiler variable sys.​year and an installer variable sys.​year
- macOS code signing: Updated code signing to include DER encoded entitlements and exec segment information. This future-proofs code signing on macOS and raises the minimum supported macOS version to 10.​15.
- macOS app store media files: Allow "Mac Developer" and "Apple Development" certificates for code signing so you can use a developer provisioning profile for local testing

Fixed:
- Regression in 11.​0: Custom IntelliJ themes for FlatLaf look and feel were not saved correctly
- Regression in 11.​0: Using different Windows service names did not work correctly on the command line
- Regression in 11.​0: The system property "exe4j.​launchName" was not consistent when the service executable was started with the /run option
- Regression in 11.​0: When setting the "Background Color" or "Foreground Color" properties for a wizard index, the installer would throw an exception at startup
- Regression in 11.​0: In the dialog for editing version-specific JVM options, some menu items in the "Insert variable" drop-down in the toolbar had no text
- Windows installers: The parent access for the temporary folder that is created by a Windows installer is not inherited anymore. This can prevent certain DLL hijacking scenarios.
- Windows installers: Folders with non-ASCII characters could temporarily appear in the navigation bar of Windows Explorer during installation
- macOS launchers: Fixed searching for JREs from previous installations
- macOS launchers: Generate a new UUID for each UI launcher to avoid issues with "local network" permissions
- macOS app store media files: If a provisioning profile is used, add "com.​apple.​application-identifier" and "com.​apple.​developer.​team-identifier" to the entitlements so that TestFlight is enabled
- macOS single bundle archives: CFBundleVersion is now set to a timestamp to allow submitting multiple builds with the same version to the app store
- macOS media files: When code signing executables in JAR files, the ZIP method (stored/​deflated) was not preserved, which could cause issues with Spring Boot
- Unix launchers: For certain version check conditions, launcher variables were not replaced in version-specific VM options
- Unix launchers: Using launcher variables for the working directory did not always work correctly
- When adding an extension JAR file to the custom code instead of the extensions directory of the install4j installation, the i18n mechanism for extensions was unsupported
- Installers for modular applications that did not include the "java.​logging" module failed at startup
- The compiler and installer variables "sys.​time" included the hour in the 1-24 range instead of the 0-23 range