liveBook · Manning

Quarkus-run.jar

As explained in Quarkus in Action

quarkus-run.jar is the executable JAR produced by a Quarkus JVM-mode package and used to launch the packaged application.

quarkus-run.jar is the executable JAR generated when a Quarkus application is packaged for JVM mode. The ordinary application JAR is Maven output, but is not directly runnable. section 2.3

Quarkus places it under quarkus-app alongside lib, which contains externalized application dependencies referenced by the JAR manifest. Therefore, moving quarkus-run.jar also requires moving the lib directory. section 2.3

Run the packaged application

Build with ./mvnw package, quarkus build, or ./gradlew build, then run java -jar target/quarkus-app/quarkus-run.jar. The application starts in the prod profile and listens on port 8080. section 2.3

The layout also supports container images: relatively stable dependencies can occupy a separate Docker layer from the changing application JAR. Generated JVM Dockerfiles apply this arrangement. section 2.3

How Quarkus in Action covers it

How deep it goes
Explains its location, dependency manifest, non-fat-JAR structure, container layering, and execution command.
Examples
Uses target/quarkus-app/quarkus-run.jar and the java -jar command to start an HTTP application on port 8080.
What it assumes
Assumes a packaged Quarkus application and distinguishes its executable artifact from the ordinary compiled application JAR.
What you can do after
Operate a packaged Quarkus application with java -jar while preserving its accompanying dependency directory.
How it connects
Connects packaged applications with JVM mode, Maven, Gradle, Docker images, manifests, and production profiles.
Cover of Quarkus in Action
liveBookmanning.com
Read Quarkus in Action on liveBook Get the book at manning.com

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Quarkus in Action. The section links point to the parts of the book it draws on.