Run/Debug Configuration: Spring Boot
Specify the fully qualified name of the class that will be executed (passed to the JRE).
If necessary, specify the command-line options to be passed to the server JVM at the server start.
Specify arguments to be passed to the program in the format that you use in the command line. Use the same rules as for specifying the VM options.
If necessary, specify a directory that will be used by the running application. This directory is the starting point for all relative input and output paths. The project directory is specified by default.
Click Browse to create variables and specify their values.
Use classpath of module
Select the module whose classpath will be used to run the application.
Include dependencies with 'Provided' scope
Enable this option to add dependencies with the Provided scope to the runtime classpath.
By default, the newest JDK from the module dependencies is used to run applications. You can specify an alternative JDK or JRE.
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:
Enable debug output
Enables logging of the debug output by adding the
Hides the Spring Boot startup banner by adding the
Enable launch optimization
Select this option to speed up application launch. The
Enable JXM agent
Enables JMX agent that shows application endpoints data by adding the following VM options (requires Spring Boot 1.3.0 or higher):
On 'Update' action
Specify an action that the IDE will do after you click Update <application name> Application:
On frame deactivation
Specify an action that the IDE will do after you switch to another application (other than IntelliJ IDEA):
Specify active Spring profiles that you want to use in this run/debug configuration.
Use this table to specify Spring Boot configuration parameters that you want to override. Such parameters are normally defined in configuration files. Listing them in a run/debug configuration allows you to easily switch parameters by modifying the run/debug configuration instead of config files, or have multiple run/debug configurations with different parameter values.
Code Coverage tab
Use this tab to configure code coverage monitoring options.
Choose coverage runner
|Select the desired code coverage runner.|
Select this option to measure code coverage with minimal slow-down.
Select this option to collect accurate branch coverage. This mode is available for the IntelliJ IDEA code coverage runner only.
Track per test coverage
Select this check box to detect lines covered by one test and all tests covering line.
Packages and classes to record code coverage data
Click and buttons to specify classes and packages to be measured. You can also remove classes and packages from the list by selecting them in the list and clicking the button.
Enable coverage in test folders
If this check box is selected, folders marked as test are included in the code coverage analysis.
Use this tab to specify which log files generated while running or debugging must be displayed in the console of the Run/Debug tool window.
Log files to be shown in console
In this table, specify a file or a group of files that will be displayed in the Run/Debug tool window.
Save console output to file
Save console output to the specified location.
Show console when a message is printed to standard output stream
Enable the output console and bring it forward if the associated process is writing to Standard.out.
Show console when a message is printed to standard error stream
Enable the output console and bring it forward if the associated process is writing to Standard.err.
Before launch options
Use this section to specify which tasks must be carried out before starting the run/debug session. The tasks you specify will be performed in the order that they appear in the list.
Show this page
This option shows the run/debug settings before starting a run/debug session.
Activate tool window
Select the checkbox to open the Run/Debug tool window once you run the session.