Command Mode Applications

This reference covers how to write applications that run and then exit.


We recommend that you follow the instructions in the next sections and create the application step by step. However, you can go right to the completed example.

Clone the Git repository: git clone, or download an archive.

The solution is located in the getting-started-command-mode directory.

Writing Command Mode Applications

There are two different approaches that can be used to implement applications that exit.

  1. Implement QuarkusApplication and have Quarkus run this method automatically

  2. Implement QuarkusApplication and a Java main method, and use the Java main method to launch Quarkus

In this document the QuarkusApplication instance is referred to as the application main, and a class with a Java main method is the Java main.

The simplest possible command mode application with access to Quarkus API’s might appear as follows:

import io.quarkus.runtime.QuarkusApplication;
import io.quarkus.runtime.annotations.QuarkusMain;

@QuarkusMain    (1)
public class HelloWorldMain implements QuarkusApplication {
  public int run(String... args) throws Exception {   (2)
    System.out.println("Hello " + args[1]);
    return 0;
1 The @QuarkusMain annotation tells Quarkus that this is the main entry point.
2 The run method is invoked once Quarkus starts, and the application stops when it finishes.


To get access to your application beans and services, be aware that a @QuarkusMain instance is an application scoped bean by default. It has access to singletons, application and dependent scoped beans. If you want to interact with beans that requires a request scope put a @ActivateRequestContext on your run() method.

This let run() have access to methods like listAll() and query* methods on a Panache Entity. Without it you will eventually get a ContextNotActiveException when accessing such classes/beans.

Main method

If we want to use a Java main to run the application main it would look like:

import io.quarkus.runtime.Quarkus;
import io.quarkus.runtime.annotations.QuarkusMain;

public class JavaMain {

    public static void main(String... args) {, args);

This is effectively the same as running the HelloWorldMain application main directly, but has the advantage it can be run from the IDE.

If a class that implements QuarkusApplication and has a Java main then the Java main will be run.
It is recommended that a Java main perform very little logic, and just launch the application main. In development mode the Java main will run in a different ClassLoader to the main application, so may not behave as you would expect.

Multiple Main Methods

It is possible to have multiple main methods in an application, and select between them at build time. The @QuarkusMain annotation takes an optional 'name' parameter, and this can be used to select the main to run using the quarkus.package.main-class build time configuration option. If you don’t want to use annotations this can also be used to specify the fully qualified name of a main class.

By default the @QuarkusMain with no name (i.e. the empty string) will be used, and if it is not present and quarkus.package.main-class is not specified then Quarkus will automatically generate a main class that just runs the application.

The name of @QuarkusMain must be unique (including the default of the empty string). If you have multiple @QuarkusMain annotations in your application the build will fail if the names are not unique.

The command mode lifecycle

When running a command mode application the basic lifecycle is as follows:

  1. Start Quarkus

  2. Run the QuarkusApplication main method

  3. Shut down Quarkus and exit the JVM after the main method returns

Shutdown is always initiated by the application main thread returning. If you want to run some logic on startup, and then run like a normal application (i.e. not exit) then you should call Quarkus.waitForExit from the main thread (A non-command mode application is essentially just running an application that just calls waitForExit).

If you want to shut down a running application and you are not in the main thread then you should call Quarkus.asyncExit in order to unblock the main thread and initiate the shutdown process.

Development Mode

Also for command mode applications the dev mode is supported. When you run mvn quarkus:dev, the command mode application is executed.

As command mode applications will often require arguments to be passed on the commandline, this is also possible in dev mode via the quarkus.args system property. For example mvn quarkus:dev -Dquarkus.args='--help' and the same can be achieved with Gradle: ./gradlew quarkusDev --quarkus-args='--help'.

You should see the following down the bottom of the screen after the application is stopped:

Press [space] to restart, [e] to edit command line args (currently '-w --tags 1.0.1.Final'), [r] to resume testing, [o] Toggle test output, [h] for more options>

You can press the Space bar key and the application will be started again. You can also use the e hotkey to edit the command line arguments and restart your application.

Testing Command Mode Applications

Command Mode applications can be tested using the @QuarkusMainTest and @QuarkusMainIntegrationTest annotations. These work in a similar way to @QuarkusTest and @QuarkusIntegrationTest where @QuarkusMainTest will run the CLI tests within the current JVM, while QuarkusIntegrationTest is used to run the generated executable (both jars and native).

We can write a simple test for our CLI application above as follows:

import io.quarkus.test.junit.main.Launch;
import io.quarkus.test.junit.main.LaunchResult;
import io.quarkus.test.junit.main.QuarkusMainLauncher;
import io.quarkus.test.junit.main.QuarkusMainTest;
import org.junit.jupiter.api.Assertions;
import org.junit.jupiter.api.Test;

public class HelloTest {

    public void testLaunchCommand(LaunchResult result) {
        Assertions.assertEquals("Hello World", result.getOutput());

    @Launch(value = {}, exitCode = 1)
    public void testLaunchCommandFailed() {

    public void testManualLaunch(QuarkusMainLauncher launcher) {
        LaunchResult result = launcher.launch("Everyone");
        Assertions.assertEquals(0, result.exitCode());
        Assertions.assertEquals("Hello Everyone", result.getOutput());

We can then extend this with an integration test that can be used to test the native executable or runnable jar:

import io.quarkus.test.junit.main.QuarkusMainIntegrationTest;

public class HelloIT extends HelloTest {