Configure log levels explicitly.

Change-Id: I12c16bcfe485a12dc2985cfb0f5287b46a995a83
1 file changed
tree: cc6d15e8d17377b8993382822e93d69fdbdd423f
  1. gradle/
  2. mulkcms2/
  3. src/
  4. .gitignore
  5. .scalafmt.conf
  6. build.gradle
  7. gradle.properties
  8. gradlew
  9. gradlew.bat
  10. pom.xml
  11. README.md
  12. settings.gradle
README.md

mulkcms2 project

This project uses Quarkus, the Supersonic Subatomic Java Framework.

If you want to learn more about Quarkus, please visit its website: https://quarkus.io/ .

Running the application in dev mode

You can run your application in dev mode that enables live coding using:

./gradlew quarkusDev

Packaging and running the application

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

Creating a native executable

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 .