Skip to content

Releases: beryx/badass-jlink-plugin

v4.0.2

30 May 01:06
a9b1b80

Choose a tag to compare

  • fixed JPackage jvm arguments not taken from jlink launcher #351
  • updared com.gradleup.shadow for JDK 27 compatibility

v4.0.1

23 May 11:28
63bd6fd

Choose a tag to compare

  • fixed JPackage missing JVM Arguments #349
  • updated ASM, should now support Java 27
  • minor fixes and improvements

v4.0.0

28 Mar 08:55
df14fba

Choose a tag to compare

Compatibility Note

  • Gradle: Gradle version 8.14.4 or newer is required.
  • Java: supported Java versions are 17 to 26.
  • The long deprecated mergedModuleJarVersion configuration option was removed.

If you must stay on older Gradle versions:

  • Use plugin 3.2.1 for Gradle < 8.14.4
  • Use plugin 2.25.0 for Gradle < 7.0

New Features

Java 26 support

The plugin now supports running on Java versions 17 - 26.

Configuration-cache compatibility

The plugin is now compatible with Gradle's configuration-cache.

Dependency graph information is captured as serializable DependencyData at configuration time
and the task implementations no longer depend on live Project state during execution.

jlink and jpackage configuration cache reuse is now covered by functional tests.

locale filtering support for runtime images and packages

Added a new jlink.includeLocales option taking a list of BCP 47 locale tags and a new jlinkincludeLocalesFile option taking a text file with comma/newline separated language tags.
Locales from both sources are merged, normalized (for example EN-us -> en-US), and deduplicated.
The effective locales are applied to the jlink task.
When locales are configured, the plugin auto-adds jdk.localedata to jlink modules if not already present.

Top-level jpackage { ... } extension support

The jpackage { ... } extension can now be applied on top-level in addition to jlink { jpackage { ... } }.

Both entry points share the same underlying JPackageData

Other notable changes

  • Added support for Java 26.
  • Updated plugin for Gradle 10 compatibility.

Fixed Bugs

  • Fixed inability to use different launcher.name and jpackage.imageName.

  • Fixed issues caused by case-insensitive launcher/image name matching in packaging tasks.

  • Fixed secondary launcher handling issues (including secondary launcher module scenarios).

  • Fixed Gradle deprecation warnings.

  • Removed deprecated mergedModuleJarVersion and related code paths.

  • Fixed FileNotFoundException on Windows builds

  • Fixed failure on Windows when launcherName is set

v4.0.0-rc3

26 Mar 18:02
cf26db6

Choose a tag to compare

v4.0.0-rc3 Pre-release
Pre-release
  • fix: FileNotFoundException on Windows builds
  • fix: failure on Windows when launcherName is set

v4.0.0-rc2

23 Mar 13:05
590b36c

Choose a tag to compare

v4.0.0-rc2 Pre-release
Pre-release

Compatibility Note

  • Gradle: Gradle version 8.14.4 or newer is required.
  • Java: supported Java versions are 17 to 26.
  • The long deprecated mergedModuleJarVersion configuration option was removed.

If you must stay on older Gradle versions:

  • Use plugin 3.2.1 for Gradle < 8.14.4
  • Use plugin 2.25.0 for Gradle < 7.0

New Features

locale filtering support for runtime images and packages

Added a new jlink.includeLocales option taking a list of BCP 47 locale tags and a new jlinkincludeLocalesFile option taking a text file with comma/newline separated language tags.
Locales from both sources are merged, normalized (for example EN-us -> en-US), and deduplicated.
The effective locales are applied to the jlink task.
When locales are configured, the plugin auto-adds jdk.localedata to jlink modules if not already present.

Top-level jpackage { ... } extension support

The jpackage { ... } extension can now be applied on top-level in addition to jlink { jpackage { ... } }.

Both entry points share the same underlying JPackageData

Configuration-cache compatibility

The plugin is now compatible with Gradle's configuration-cache.

Dependency graph information is captured as serializable DependencyData at configuration time
and the task implementations no longer depend on live Project state during execution.

jlink and jpackage configuration cache reuse is now covered by functional tests.

Other notable changes

  • Added support for Java 26.
  • Updated plugin for Gradle 10 compatibility.

Fixed Bugs

  • Fixed inability to use different launcher.name and jpackage.imageName.

  • Fixed issues caused by case-insensitive launcher/image name matching in packaging tasks.

  • Fixed secondary launcher handling issues (including secondary launcher module scenarios).

  • Fixed Gradle deprecation warnings.

  • Removed deprecated mergedModuleJarVersion and related code paths.

v3.2.1

29 Jan 23:48
804db42

Choose a tag to compare

fix #326

v3.2.0

20 Dec 06:32
c3e5bab

Choose a tag to compare

What's Changed

Full Changelog: v3.1.4...v3.2.0

v3.1.4-rc

28 Sep 11:43
b602f9d

Choose a tag to compare

v3.1.4-rc Pre-release
Pre-release

What's Changed

  • Add compatibility with Temurin JDK 25 (JEP 493)
  • Bump actions/setup-java from 4 to 5 by @dependabot[bot] in #309
  • Bump org.kohsuke:github-api from 1.327 to 1.329 by @dependabot[bot] in #307
  • Bump org.asciidoctor.jvm.convert from 4.0.4 to 4.0.5 by @dependabot[bot] in #310
  • Bump actions/checkout from 4 to 5 by @dependabot[bot] in #308
  • Bump org.kohsuke:github-api from 1.329 to 1.330 by @dependabot[bot] in #312
  • Bump com.github.ben-manes.versions from 0.52.0 to 0.53.0 by @dependabot[bot] in #313

Full Changelog: v3.1.3...v3.1.4-rc

v3.1.3

28 Sep 11:40
f17f33f

Choose a tag to compare

Full Changelog: v3.1.2...v3.1.3

v3.1.2

03 Aug 03:45
df40107

Choose a tag to compare

This release adds Gradle 9 compatibiblity.