| commit | 84db379e6806b7c4603a9f86452ee3d8a1fd7e0b | [log] [tgz] |
|---|---|---|
| author | Matthias Andreas Benkard <code@mail.matthias.benkard.de> | Sun Mar 15 12:48:29 2020 +0100 |
| committer | Matthias Andreas Benkard <code@mail.matthias.benkard.de> | Mon Mar 16 11:13:16 2020 +0100 |
| tree | 7b5d5b4ae2dd0e952493211191f3ae6ab3f25a82 | |
| parent | 2ebeae10dc3fdef90a769c133251632d7cb9aec9 [diff] |
Disable Quarkus Kubernetes processing. In Quarkus 1.3.0.Final, Kubernetes processing causes the build to fail. As it was buggy before, this patch disables it for now. Change-Id: I9dd6a15a968846932f373598e50e1f2846679564
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 .