java-tutorials/quarkus-jandex/hello-app
Ralf Ueberfuhr c034fb74bc BAEL-5036: Add Quarkus Hello App that uses several external modules that contain CDI managed beans. Each module is indexed using a different kind of registration. 2021-10-20 14:14:40 +02:00
..
.mvn/wrapper BAEL-5036: Add Quarkus Hello App that uses several external modules that contain CDI managed beans. Each module is indexed using a different kind of registration. 2021-10-20 14:14:40 +02:00
src/main BAEL-5036: Add Quarkus Hello App that uses several external modules that contain CDI managed beans. Each module is indexed using a different kind of registration. 2021-10-20 14:14:40 +02:00
.dockerignore BAEL-5036: Add Quarkus Hello App that uses several external modules that contain CDI managed beans. Each module is indexed using a different kind of registration. 2021-10-20 14:14:40 +02:00
.gitignore BAEL-5036: Add Quarkus Hello App that uses several external modules that contain CDI managed beans. Each module is indexed using a different kind of registration. 2021-10-20 14:14:40 +02:00
README.md BAEL-5036: Add Quarkus Hello App that uses several external modules that contain CDI managed beans. Each module is indexed using a different kind of registration. 2021-10-20 14:14:40 +02:00
mvnw BAEL-5036: Add Quarkus Hello App that uses several external modules that contain CDI managed beans. Each module is indexed using a different kind of registration. 2021-10-20 14:14:40 +02:00
mvnw.cmd BAEL-5036: Add Quarkus Hello App that uses several external modules that contain CDI managed beans. Each module is indexed using a different kind of registration. 2021-10-20 14:14:40 +02:00
pom.xml BAEL-5036: Add Quarkus Hello App that uses several external modules that contain CDI managed beans. Each module is indexed using a different kind of registration. 2021-10-20 14:14:40 +02:00

README.md

Hello App with Quarkus

Running the application in dev mode

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

./mvnw compile quarkus:dev

You can then find the app using http://localhost:8080.

NOTE: Quarkus now ships with a Dev UI, which is available in dev mode only at http://localhost:8080/q/dev/.

Packaging and running the application

The application can be packaged using:

./mvnw package

It produces the quarkus-run.jar file in the target/quarkus-app/ directory. Be aware that its not an über-jar as the dependencies are copied into the target/quarkus-app/lib/ directory.

The application is now runnable using java -jar target/quarkus-app/quarkus-run.jar.

If you want to build an über-jar, execute the following command:

./mvnw package -Dquarkus.package.type=uber-jar

The application, packaged as an über-jar, is now runnable using java -jar target/*-runner.jar.

Creating a native executable

You can create a native executable using:

./mvnw package -Pnative

Or, if you don't have GraalVM installed, you can run the native executable build in a container using:

./mvnw package -Pnative -Dquarkus.native.container-build=true

You can then execute your native executable with: ./target/quarkus-sample-1.0-SNAPSHOT-runner

If you want to learn more about building native executables, please consult https://quarkus.io/guides/maven-tooling.html.