Skip to content
Custom runtime image of spring-petclinic using the badass-jlink plugin
CSS Java
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
gradle/wrapper
resources
.gitignore
.travis.yml
LICENSE
README.md
build.gradle
gradle.properties
gradlew
gradlew.bat
settings.gradle

README.md

PRs Welcome License Build Status

Custom runtime image of spring-petclinic using the badass-jlink plugin

This project demonstrates the capabilities of the Badass JLink Plugin by creating a custom runtime image of the Spring PetClinic.

⚠️ The Spring PetClinic is an application for which modularization does more harm than good. (This comment applies to the Spring PetClinic version used by this project, which is based on Spring Boot 2.0.4. It may not be valid for newer versions.) The goal of this project is only to show that it is possible to modularize the Spring PetClinic and subsequently use the Badass-JLink plugin to create a custom runtime image of it. A better approach for creating a custom runtime image of the Spring PetClinic is to use the Badass Runtime Plugin, as shown in this example project.

Quick start

From the releases page download the archived custom runtime image for your operating system. Unpack the archive and execute the spring-petclinic script found in the spring-petclinic-image/bin directory.
Then, access http://localhost:8080/ in your browser.

Creating a custom runtime image

Gradle must use Java 11 in order to be able to build the project. To create the custom runtime image execute:

./gradlew jlinkZip

This command creates the runtime image in the build/spring-petclinic-image directory and a zip file of it in build/image-zip.

The start scripts are found in the build/spring-petclinic-image/bin directory.

You can’t perform that action at this time.