commit | 188327df8235e114962a7ccf5895999eab2e3470 | [log] [tgz] |
---|---|---|
author | Matthias Andreas Benkard <code@mail.matthias.benkard.de> | Fri Apr 17 21:22:57 2020 +0200 |
committer | Matthias Andreas Benkard <code@mail.matthias.benkard.de> | Fri Apr 17 21:22:57 2020 +0200 |
tree | 1d743fbec7b54a9bb700484463be17e83349b82d | |
parent | 0fb9d12078b07947f8df732564477bd3f8eabaea [diff] |
Update to Quarkus 1.3.2.Final. Also adds a workaround for Quarkus issue #8662 (https://github.com/quarkusio/quarkus/issues/8662). Change-Id: I0a91a67609b0fce4cf7f4dd356d787caf1e2938d
This project uses Quarkus, the Supersonic Subatomic Java Framework.
If you want to learn more about Quarkus, please visit its website: https://quarkus.io/ .
You can run your application in dev mode that enables live coding using:
./gradlew quarkusDev
The application is packageable using ./gradlew quarkusBuild
. It produces the executable mulkcms2-1.0.0-SNAPSHOT-runner.jar
file in build
directory. Be aware that it’s not an über-jar as the dependencies are copied into the build/lib
directory.
The application is now runnable using java -jar build/mulkcms2-1.0.0-SNAPSHOT-runner.jar
.
If you want to build an über-jar, just add the --uber-jar
option to the command line:
./gradlew quarkusBuild --uber-jar
You can create a native executable using: ./gradlew buildNative
.
Or you can use Docker to build the native executable using: ./gradlew buildNative --docker-build=true
.
You can then execute your binary: ./build/mulkcms2-1.0.0-SNAPSHOT-runner
If you want to learn more about building native executables, please consult https://quarkus.io/guides/gradle-tooling#building-a-native-executable .