From 8c5047cf7f6a7a13d48db9d4d6d0f7584b0a6cab Mon Sep 17 00:00:00 2001 From: Matthias Andreas Benkard Date: Sat, 18 Apr 2020 08:14:16 +0200 Subject: Replace the autogenerated README.md with a new README.adoc. Change-Id: I8799855bd21e3b6fc2a28b4b42ba0e5a6134bdbb --- README.md | 35 ----------------------------------- 1 file changed, 35 deletions(-) delete mode 100644 README.md (limited to 'README.md') diff --git a/README.md b/README.md deleted file mode 100644 index 1cb0c25..0000000 --- a/README.md +++ /dev/null @@ -1,35 +0,0 @@ -# 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 . \ No newline at end of file -- cgit v1.2.3