Skip to content

Conversation

lukaszlenart
Copy link
Collaborator

@lukaszlenart lukaszlenart commented Nov 19, 2022

Please see the docs for changes of the configuration options:

  • Removed <bundledJreAsFallback>, path search is always first and registry search second in order to improve compatibility with modern runtimes.
  • Replaced <bundledJre64Bit> and <runtimeBits> with <requires64Bit> which works during path and registry search.
  • Replaced <jdkPreference> with <requiresJdk> which works during path and registry search.
  • Replaced <bundledJreErr> with <jreNotFoundErr>.
  • <minVersion> and <maxVersion> are now used during path and registry search, previously they were only checked during registry search.

The plugin will show warnings when these options are still used:

[WARNING] <bundledJreAsFallback/> has been removed! It has no effect!
[WARNING] <bundledJre64Bit/> is deprecated, use <requires64Bit/> instead!
[WARNING] <runtimeBits/> is deprecated, use <requires64Bit/> instead!
[WARNING] <jdkPreference/> is deprecated, use <requiresJdk/> instead!
[WARNING] <bundledJreErr/> is deprecated, use <jreNotFoundErr/> instead!

Closes #199

@lukaszlenart
Copy link
Collaborator Author

I have tested this change using this project (even using Docker maven:3.8-openjdk-8) and everything is fine when running on the latest Maven version.

@lukaszlenart lukaszlenart merged commit 0a7d1f0 into master Nov 21, 2022
@lukaszlenart lukaszlenart deleted the launch4j-350 branch November 21, 2022 10:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update to Launch4J 3.50
1 participant