Using this Gradle plugin you can create a custom runtime image of your modular application with minimal effort, even if it depends on automatic modules.
💡 For non-modular applications use the Badass-Runtime plugin.
Badass-JLink exposes an extension with the name jlink
to let you configure various
aspects of its operation.
A simple example configuration is shown below:
jlink {
options = ['--strip-debug', '--compress', '2', '--no-header-files', '--no-man-pages']
launcher{
name = 'hello'
jvmArgs = ['-Dlog4j.configurationFile=./log4j2.xml']
}
}
The following projects illustrate how to use this plugin to create custom runtime images:
- badass-jlink-example - a 'Hello world' application using slf4j and logback.
- badass-jlink-example-log4j2-javafx - a 'Hello world' JavaFX application using log4j2.
- badass-jlink-example-kotlin-javafx - a 'Hello world' JavaFX application written in Kotlin.
- badass-jlink-example-kotlin-tornadofx - a 'Hello world' application written in Kotlin using tornadofx.
- badass-jlink-spring-petclinic - creates a custom runtime image of the Spring PetClinic application.
- copper-modular-demo - creates a custom runtime image of a COPPER 5 modular application.
This is a complex plugin. Please read the documentation before using it.
See the list of all releases if you use an older version of this plugin.