Spring Boot run configuration

Active profiles

Specify which Spring profiles should be active.

This passes -Dspring.profiles.active on the command line, which overrides the spring.profiles.active property.

For more information, refer to Spring Boot: Profiles.

Enable debug output

Enable logging of the debug output.

This passes -Ddebug on the command line, which is similar to setting the debug property.

For more information, refer to Spring Boot: Logging.

Hide banner

Disable the start-up banner entirely.

This passes -Dspring.main.banner-mode=OFF on the command line, which is similar to setting the spring.main.banner-mode property to off.

For more information, refer to Spring Boot: Customizing the banner.

Disable launch optimization

Do not speed up the start-up time of your application.

By default, this optimization is enabled by passing the following JVM options on the command line: -XX:TieredStopAtLevel=1 and -noverify (the latter is deprecated in JDK 13 and later versions). This decreases the start-up time of the application at the expense of long-term performance and security. You can keep it enabled for development environments but disable it for production runs.

Disable JMX endpoints

Disable the JMX agent that shows the application endpoints data in the Actuator tab of the Run tool window.

By default, the JMX agent is enabled by passing the following JVM options on the command line:

• -Dcom.sun.management.jmxremote

• -Dspring.jmx.enabled=true

• -DSpring.liveBeansView.mbeanDomain

• -Dspring.application.admin.enabled=true

• -Dmanagement.endpoints.jmx.exposure.include=*

This slows down the application startup. If you disable the JMX agent, the above options will not be added to the command line.

For more information, refer to Spring: JMX

On 'Update' action

Specify what to do when you modify the code and want to update the running application:

• Do nothing: Do not update the application.

• Update resources: Update all modified resource files.

• Update classes and resources: Update all modified resource files and recompile all changed Java classes.

  When debugging, IntelliJ IDEA will deploy and reload updated classes. For more information, refer to Reload modified classes. Otherwise, when running the application regularly, IntelliJ IDEA will only update the changed classes in the output folder. Whether it will deploy and reload such classes in the running application depends on the capabilities of the Java runtime that you are using.

• Update trigger file: Pass -Dspring.devtools.restart.trigger-file=.restartTriggerFile on the command line and update the .restartTriggerFile file, which will initiate a restart check: the application will restart only if there is something to do.

• Hot swap classes and update trigger file if failed: This is similar to Update classes and resources followed by Update trigger file.

On frame deactivation:

Specify what to do when you switch from IntelliJ IDEA to another application (for example, a web browser):

• Do nothing: Do not update the application.

• Update resources: Update all modified resource files.

• Update classes and resources: Update all modified resource files and recompile all changed Java classes.

  When debugging, IntelliJ IDEA will deploy and reload updated classes. For more information, refer to Reload modified classes. Otherwise, when running the application regularly, IntelliJ IDEA will only update the changed classes in the output folder. Whether it will deploy and reload such classes in the running application depends on the capabilities of the Java runtime that you are using.

Override configuration properties

Override any configuration property by passing it as a JVM option. For example, if you override the value of the spring.config.name property with my.config, IntelliJ IDEA will pass -Dspring.config.name=my.config on the command line when running this Spring Boot application.

Allow multiple instances

Allow multiple instances of this run configuration to execute at the same time. By default, this option is disabled, which means that when you run the configuration, other active sessions of the configuration will terminate.

Working directory

Specify the directory that will be used for all relative input and output paths. By default, IntelliJ IDEA uses the project root as the working directory.

Environment variables

Specify the names and values of environment variables that are necessary when running this configuration.

Do not build before run

Run the application straight away without launching the build process.

Use classpath of module

Select the module whose classpath should be used to run the application.

Modify classpath

If necessary, specify another classpath or select dependencies that you want to exclude from the classpath. This option is necessary in cases when the runtime classpath is different from the compile classpath (debug libraries, different locations, and so on).

Use the and buttons to sort dependencies on the list. The order of dependencies is important as IntelliJ IDEA will process them in the same order as they are specified in the list.

VM options

Specify the options to be passed to the Java virtual machine when launching the application, for example, -mx, -verbose, and so on.

When specifying JVM options, follow these rules:

• Use spaces to separate individual options.

• If the value of an option includes spaces, enclose either the value or the actual spaces with double quotes.

• If an option includes double quotes as part of the value, escape the double quotes using backslashes.

• You can pass environment variable values to custom Java properties.

Use code completion in this field: start typing the name of a flag, and the IDE suggests a list of available command line options. This works for -XX: and -X options and some standard options that are not configured by IntelliJ IDEA automatically, like -ea, but not for -cp or –release.

The -classpath option specified in this field overrides the classpath of the module.

Program arguments

Pass command-line arguments to your application.

Add dependencies with “provided” scope to classpath

Add the dependencies with the provided scope to the runtime classpath.

This option is enabled by default in Spring Boot run configurations.

Shorten command line

Select a method that will be used to shorten the command line if the classpath gets too long, or you have many VM arguments that exceed your OS command line length limitation. The choice of option depends on the class loader implementation. Note that some frameworks do not support JAR manifest, while other frameworks with custom class loaders will not work well with the classpath.file option.

• none: IntelliJ IDEA will not shorten a long classpath. If the command line exceeds the OS limitation, IntelliJ IDEA will be unable to run your application and will display a message suggesting that you specify the shortening method.

• JAR manifest: IntelliJ IDEA will pass a long classpath via a temporary classpath.jar. The original classpath is defined in the manifest file as a class-path attribute in classpath.jar. Note that you will be able to preview the full command line if it was shortened using this method, not just the classpath of the temporary classpath.jar.

• classpath.file: IntelliJ IDEA will write a long classpath into a text file.

• @argFiles (Java 9+): the command-line length limitations will be overcome using the @argument files option.