| commit | 944c0b663340a6cea517d0ee1542fbb6ad4c94e6 | [log] [tgz] |
|---|---|---|
| author | Matthias Andreas Benkard <code@mail.matthias.benkard.de> | Sun Feb 02 13:17:48 2020 +0100 |
| committer | Matthias Andreas Benkard <code@mail.matthias.benkard.de> | Sun Feb 02 13:17:48 2020 +0100 |
| tree | e1dc3cb9f455c77a03545c86af1a6585b98a7651 | |
| parent | 9aab180b33c16ae56d79c9e67b258588505f0962 [diff] |
Remove the JWT cookie filters again. They were pointless: quarkus-oidc's CodeAuthenticationMechanism already takes care of setting a session cookie, which it uses in preference over an IdP redirect. The reason the cookie did not stick before is still unclear, but it was fixed by tweaking the Keycloak settings for the MulkCMS client. Change-Id: Ie547ee0af23b6532515a990c2699ba9ffa686a5a
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 .