| commit | 57c9a8aa7845f27cee62c423c7128b46d256fc40 | [log] [tgz] |
|---|---|---|
| author | Matthias Andreas Benkard <code@mail.matthias.benkard.de> | Fri Jan 24 19:09:38 2020 +0100 |
| committer | Matthias Andreas Benkard <code@mail.matthias.benkard.de> | Fri Jan 24 19:09:38 2020 +0100 |
| tree | 80151b1d6be8adf8a916df7d41cf39ca5197926e | |
| parent | fb769c2d96513a5e7111e195b1b7b3d5d61e8bbb [diff] |
Assume that Benki entities are in the “benki” schema. Since PostgreSQL does not support multiplexing access to several databases through one connection, everything is easier if all data lives in separate schemas in the same database. This change modifies the Hibernate entities accordingly. Change-Id: Ibe410ab340d77f35549208daf59a15520805c23a
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 .