Run/Debug Configuration: Maven
This run/debug configuration is used to launch the Maven projects. The dialog box contains the following tabs:
| 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 |
| Use plugin registry | Check this option to enable referring to the Maven Plugin Registry. This option corresponds to the |
| Execute goals recursively | If this option is cleared, the build does not recur into the nested projects. Clearing this option equals to |
| Print exception stack traces | If this option is checked, exception stack traces are generated. This option corresponds to the |
| 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:
|
| Plugin update policy | Select plugin update policy from the drop-down list. You can opt to:
|
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:
|
| 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 check boxes 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:
|
| Skip Content | Select this check box to have the previous content of the selected log skipped. |
| Save console output to file | Select this check box 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 check box 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 check box 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 options
When you edit a run configuration (but not a run configuration template), you can specify the following options for it:
| Item | Description |
|---|---|
| Name | In this text box, 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 | Select this check box to make the run/debug configuration 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 If the file-based format is used, the settings are stored in the |
Toolbar
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. |
 | Edit Templates | View and edit the default template for the selected run/debug configuration. The templates are 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 Then, to move a configuration into a folder, between the folders or out of a folder, use drag-and-drop or To remove grouping, select a folder and click |
 | Sort configurations | Click this button to sort configurations in the alphabetical order. |
, and specify folder name. If only a category is in focus, an empty folder is created. Templates
Under the Templates node in the tree view of run configurations, you can select a run configuration template and edit its default settings. This will not affect the configurations that are already created, but will be used as defaults when creating new configurations of the corresponding type.
When you select the Templates node itself, you will be able to adjust general settings that apply to all run/debug configurations:
| Item | Description |
|---|---|
| Configurations available in Run Dashboard | In this section you can create a list of run configurations available in the Run Dashboard — a tool window that helps you execute and manage multiple run/debug configurations. Note that the dashboard will only display the configuration types for which you have created one ore more configurations. |
| Confirm rerun with process termination | The behavior of this checkbox depends on whether the Single instance only option is selected for a particular run/debug configuration.
|
| Temporary configurations limit | Specify the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list. |
on the main toolbar) while another process is still running, results in showing a dialog box prompting to terminate the current process before launching a new one. Before Launch options
In this area you can specify tasks that must be 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:
|
| 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 | If this checkbox is selected, which it is by default, the Run or the Debug tool window opens when you start the run/debug configuration. Otherwise, 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. |
