Run/Debug Configuration: Maven

This run/debug configuration is used to launch the Maven projects. The dialog box contains the following tabs:

Parameters tab
General tab
Runner tab

Item	Description
Name	In this text box, specify the name of the current run/debug configuration.

Parameters tab

Item	Description
Working directory	Specify the path to the Maven project file pom.xml.
Command line	Specify the Maven goals and options separated with space.
Profiles	Specify the profiles to be used separated with space.
Resolve Workspace Artifacts	We recommend that you use this checkbox if you have dependent modules in your project. By default, this checkbox is not selected. In this case, classes of dependent modules are searched in .jar files in a Maven local repository. If you select this checkbox, the classes of the dependent modules will be searched in the module compilation output. In this case, each time you make changes to the dependent module, you don't need to deploy them into a local repository.

General

Item	Description
Work offline	If this option is checked, Maven works in the offline mode and uses only those resources that are available locally. This option corresponds to the `--offline` command line option.
Use plugin registry	Check this option to enable referring to the Maven Plugin Registry. This option corresponds to the `--no-plugin-registry` command line option.
Execute goals recursively	If this option is cleared, the build does not recur into the nested projects. Clearing this option equals to `--non-recursive` command line option.
Print exception stack traces	If this option is checked, exception stack traces are generated. This option corresponds to the `--errors` command line option.
Always update snapshots	Select this checkbox to always update snapshot dependencies.
Output level	Select the desired level of the output log, which allows plugins to create messages at levels of debug, info, warn, and error, or disable output log.
Checksum policy	Select the desired level of checksum matching while downloading artifacts. You can opt to fails downloading, when checksums do not match `--strict-checksums`, or issue a warning `--lax-checksums`.
Multiproject build fail policy	Specify how to treat a failure in a multiproject build. You can choose to: Fail the build at the very first failure, which corresponds to the command line option `--fail-fast`. Fail the build at the end, which corresponds to the command line option `--fail-at-end`. Ignore failures, which corresponds to the command line option `--fail-never`.
Plugin update policy	Select plugin update policy from the drop-down list. You can opt to: Check for updates, which corresponds to the command line option `--check-plugin-updates`. Suppress checking for updates, which corresponds to the command line option `--no-plugin-updates`.
Threads `(-T option)`	Use this field to set the `-T` option for parallel builds. This option is available for Maven 3 and later versions. For more information, see parallel builds in Maven 3 feature.
Maven home directory	Use this drop-down list to select a bundled Maven version that is available (for Maven2, version 2.2.1 and for Maven3, version 3.0.5) or the result of resolved system variables such as `MAVEN_HOME` or `MAVEN2_HOME`. You can also specify your own Maven version that is installed on your machine. You can click and select the necessary directory in the dialog that opens.
User settings file	Specify the file that contains user-specific configuration for Maven in the text field. If you need to specify another file, check the Override option, click the ellipsis button and select the desired file in the Select Maven Settings File dialog.
Local repository	By default, the field shows the path to the local directory under the user home that stores the downloads and contains the temporary build artifacts that you have not yet released. If you need to specify another directory, check the Override option, click the ellipsis button and select the desired path in the Select Maven Local Repository dialog.

Runner tab

Item	Description
VM Options	Specify the string passed to the VM for launching the Maven project. When specifying JVM options, follow these rules: Use spaces to separate individual options, for example, `-client -ea -Xmx1024m`. If an option includes spaces, enclose the spaces or the argument that contains spaces in double quotes, for example, `some" "arg` or `"some arg"`. If an option includes double quotes (as part of the argument), escape the double quotes using backslashes, for example, `-Dmy.prop=\"quoted_value\"`. You can pass environment variable values to custom Java properties. For example, if you define a variable `MY_ENV_VAR`, you can pass it to the `foo` property as follows: -Dfoo=${MY_ENV_VAR}
JRE	Select JRE from the drop-down list.
Skip tests	If this option is checked, the tests will be skipped when running or debugging the Maven project.
Environment variables	Click Browse to open the Environment Variables dialog box, where you can create variables and specify their values.
Properties	Specify the properties and their values to be passed to Maven.

Logs tab

Use this tab to specify which log files generated while running or debugging should be displayed in the console, that is, on the dedicated tabs of the Run or Debug tool window.

Item	Description
Is Active	Select checkboxes in this column to have the log entries displayed in the corresponding tabs in the Run tool window or Debug tool window.
Log File Entry	The read-only fields in this column list the log files to show. The list can contain: Full paths to specific files. Ant patterns that define the range of files to be displayed. Aliases to substitute for full paths or patterns. These aliases are also displayed in the headers of the tabs where the corresponding log files are shown. If a log entry pattern defines more than one file, the tab header shows the name of the file instead of the log entry alias.
Skip Content	Select this checkbox to have the previous content of the selected log skipped.
Save console output to file	Select this checkbox to save the console output to the specified location. Type the path manually, or click the browse button and point to the desired location in the dialog that opens.
Show console when a message is printed to standard output stream	Select this checkbox to activate the output console and bring it forward if an associated process writes to Standard.out.
Show console when a message is printed to standard error stream	Select this checkbox to activate the output console and bring it forward if an associated process writes to Standard.err.
	Click this button to open the Edit Log Files Aliases dialog where you can select a new log entry and specify an alias for it.
	Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog.
	Click this button to remove the selected log entry from the list.

Common

When you edit a run configuration (but not a run configuration template), you can specify the following options:

Item	Description
Name	In this field, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example, from the Run popup `Shift+Alt+F10`.
Share through VCS	Select this checkbox to put the run/debug configuration under version control and make it available to other team members. If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate .xml file in the .idea\runConfigurations folder if the run/debug configuration is shared, or in the .idea\workspace.xml file otherwise. If the file-based format is used, the settings are stored in the .ipr file for shared configurations, or in the .iws file otherwise.
Allow running in parallel	If this checkbox is selected, it is possible to launch a run configuration multiple times in parallel instead of rerunning it. Each runner will start in its own tab of the Run Tool Window or Debug Tool Window. When disabled, every time a new instance of the run/debug configuration is launched, IntelliJ IDEA checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog. If you click OK in the confirmation dialog, the first instance of the runner will be stopped, and the next one will take its place. This makes sense when launching two instances of run/debug configurations of the same type consumes too much of the CPU and memory resources..

Item

Description

Name

In this field, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example, from the Run popup Shift+Alt+F10.

Share through VCS

Select this checkbox to put the run/debug configuration under version control and make it available to other team members.

If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate .xml file in the .idea\runConfigurations folder if the run/debug configuration is shared, or in the .idea\workspace.xml file otherwise.

If the file-based format is used, the settings are stored in the .ipr file for shared configurations, or in the .iws file otherwise.

Allow running in parallel

If this checkbox is selected, it is possible to launch a run configuration multiple times in parallel instead of rerunning it. Each runner will start in its own tab of the Run Tool Window or Debug Tool Window.

When disabled, every time a new instance of the run/debug configuration is launched, IntelliJ IDEA checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog. If you click OK in the confirmation dialog, the first instance of the runner will be stopped, and the next one will take its place. This makes sense when launching two instances of run/debug configurations of the same type consumes too much of the CPU and memory resources..

The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.

Item	Shortcut	Description
	`Alt+Insert`	Create a run/debug configuration.
	`Alt+Delete`	Delete the selected run/debug configuration. Note that you cannot delete default configurations.
	`Ctrl+D`	Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
		The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.
		View and edit the template (that is, the default run/debug configuration settings). The templates are displayed under the Templates node and used for newly created configurations.
/	`Alt+Up`/`Alt+Down`	Move the selected run/debug configuration up and down in the list. The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration. Default templates of run/debug configurations are always sorted alphabetically.
		Move into new folder / Create new folder. You can group run/debug configurations by placing them into folders. To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created. Then, to move a configuration into a folder, between the folders or out of a folder, use drag or and buttons. To remove grouping, select a folder and click .
		Click this button to sort configurations in the alphabetical order.

Before Launch

In this area you can specify tasks that must be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.

Item	Shortcut	Description
	`Alt+Insert`	Click this icon to add one of the following available tasks: Run External tool: select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in IntelliJ IDEA yet, add its definition. For more information, see External tools and External Tools. Run Another Configuration: select to execute another run/debug configuration. In the dialog that opens, select the configuration to be run. Build: select to compile the specified module. The Build Module command will be executed. If an error occurs during compilation, IntelliJ IDEA won't attempt to start the run/debug configuration. Build Project: select to compile the entire project. The Build Project command will be executed. If an error occurs during compilation, IntelliJ IDEA won't attempt to start the run/debug configuration. Build, no error check: the same as the Build option, but IntelliJ IDEA will try to start the run/debug configuration irrespective of the compilation results. Build Artifacts: select this option to build an artifact or artifacts. In the dialog that opens, select the artifact or artifacts that should be built. Launch Web Browser: select this option to have a browser started. In the dialog that opens, select the type of the browser and provide the start URL. Also, specify if you want the browser be launched with JavaScript debugger. Run Ant target: select this option to run an Ant target. In the dialog that opens, select the target to be run. Run Grunt task: select this option to run a Grunt task. In the Grunt task dialog that opens, specify the Gruntfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Grunt tool. Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the grunt-cli package. Run Gulp task: select this option to run a Gulp task. In the Gulp task dialog that opens, specify the Gulpfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Gulp tool. Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the gulp package. Run Maven Goal: select this option to run a Maven goal. In the dialog that opens, select the goal to be run. Run npm Script: select this option to execute an npm script. In the NPM Script dialog that opens, specify the npm run/debug configuration settings. Generate CoffeeScript Source Maps: select this option to generate the source maps for your CoffeeScript sources. In the dialog that opens, specify where your CoffeeScript source files are located. Run Remote External tool: adds a remote SSH external tool.
	`Alt+Delete`	Click this icon to remove the selected task from the list.
	`Enter`	Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
/	`Alt+Up`/`Alt+Down`	Click these icons to move the selected task one line up or down in the list. (The tasks are performed in the order that they appear in the list.)
Show this page		Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.
Activate tool window		By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration. Otherwise, if the checkbox is cleared, the tool window isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing `Alt+4` or `Alt+5`.

Last modified: 20 March 2020