Skip to content

Releases: beryx/badass-jlink-plugin

v3.1.1

22 Nov 13:49
Compare
Choose a tag to compare
  • fix #282: 3.1.0 is released but not published
  • fix #279: Module name cannot be determined if module declaration is annotated

v3.1.0

11 Nov 12:47
Compare
Choose a tag to compare

no changes since v3.1.0-rc-1

v3.1.0-rc-1

05 Nov 16:42
Compare
Choose a tag to compare
v3.1.0-rc-1 Pre-release
Pre-release
  • release Java 23 compatible version #275
  • secondary Launcher fails with application main class missing in Kotlin DSL #244
  • Apply plugin in multi project gradle configure error #265

v3.0.1

26 Oct 01:47
Compare
Choose a tag to compare
  • Bump asm to 9.6
  • Fix jpackageImage and jpackage task inputs

badass-jlink-plugin-3.0.0

25 Sep 02:11
Compare
Choose a tag to compare
  • Support Java 21 (#238)
  • Minimum JDK is now 17 and Gradle is 7.4
  • Fix incorrect jpackage/jpackageImage inputs/outputs (#237)
  • Read module-info.class anywhere in jar file (#224)
  • Do not require mainClass and moduleName to be set in secondaryLauncher (#213)
  • Added iconOpts to the jpackage commandline (#235) by @showbags
  • Replace deprecated API usages
  • Remove unnecessary plugin dependencies

badass-jlink-plugin-2.26.0

25 Dec 01:54
Compare
Choose a tag to compare
  • support Java 19 (thanks to @xzel23)

badass-jlink-plugin-2.25.0

04 Mar 09:43
Compare
Choose a tag to compare

badass-jlink-plugin-2.24.4

20 Oct 15:15
Compare
Choose a tag to compare
  • issue #200: createMergedModule fails with synthetic Service Providers

badass-jlink-plugin-2.24.3

19 Oct 21:31
Compare
Choose a tag to compare
  • issue #199: Version 2.24.2 fails with Unresolved reference: jvmArgs

badass-jlink-plugin-2.24.2

16 Sep 14:30
Compare
Choose a tag to compare
  • issue #197: application.applicationDefaultJvmArgs not taking effect in launcher