This run/debug configuration is used to launch the Maven projects. The dialog box contains the following tabs:
|Name||In this text box, specify the name of the current run/debug configuration.|
|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 check box if you have dependent modules in your project.
By default, this check box is not selected. In this case, classes of dependent modules are searched in .jar files in a Maven local repository. If you select this check box, 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.
|Work offline||If this option is checked, Maven works in 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.
|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:
|Snapshot update policy||Specify whether the snapshot dependencies should be updated.|
|Plugin update policy||
Select plugin update policy from the drop-down list. You can opt to:
|Maven home directory||By default, this field shows the fully qualified name of the Maven installation directory. If you need to specify another directory, check the Override option, click the ellipsis button and select the desired path in the Select Maven Installation Directory dialog.|
|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.|
|VM Options||Specify the string passed to the VM for launching the Maven project.
When specifying the 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.|
|Properties||Specify the properties and their values to be passed to Maven.|
|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 standard out changes||Select this check box to activate output console and bring it forward, if associated process writes to Standard.out.|
|Show console when standard error changes||Select this check box to activate output console and bring it forward, if 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.|
Click this button to edit the select log file entry.
The button is available only when an entry is selected.
|Alt+InsertAlt+InsertAlt+InsertAlt+InsertAlt+InsertAlt+InsertCtrl+N or Alt+InsertAlt+InsertAlt+InsertCommand N or Control EnterControl N or Control EnterCommand N or Control Enter||Click this button to add new configuration to the list.|
|Alt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteCommand Delete or Command BackspaceCommand DeleteCommand Delete or Command Backspace||Click this button to remove the selected configuration from the list.|
|Ctrl+DCtrl+DCtrl+DCtrl+DMeta+DCtrl+DCtrl+DCtrl+D, Ctrl+Shift+Down or Ctrl+Shift+UpCtrl+DCommand DCommand DCommand D||Click this button to create a copy of the selected configuration.|
|Edit defaults||Click this button to edit the default configuration templates. The defaults are used for the newly created configurations.|
|or||Alt+UpAlt+UpAlt+UpAlt+UpAlt+Up or Ctrl+Alt+AAlt+UpAlt+UpCtrl+Alt+UpCtrl+Shift+UpControl UpControl UpControl Alt Up or Alt+DownAlt+DownAlt+DownAlt+DownAlt+Down or Ctrl+Alt+EAlt+DownAlt+DownCtrl+Alt+DownCtrl+Shift+DownControl DownControl DownControl Alt Down||Use these buttons to move the selected configuration or group of configurations (folder) up and down in the list.
The order of configurations or folders in the list defines the order, in which configurations appear in the Run/Debug drop-down list on the main toolbar.
|Use this button to create a new folder.
If one or more run/debug configurations have the focus, then the selected run/debug configurations are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created.
Move run/debug configurations to a folder using drag-and-drop, or buttons.
|Name||In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.|
|Defaults||This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations.|
|Temporary configurations limit||Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.|
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 .idea\runConfigurations folder if the run/debug configuration is shared and 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 for the ones that are not shared.
This check box is not available when editing the run/debug configuration defaults.
|Single instance only||If this check box is selected, this run/debug configuration cannot be launched more than once.
Every time a new 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 box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place.
This make sense, when usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources.
If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window.
|Before launch||Specify which tasks should be carried out before starting the run/debug configuration.
The specified tasks are performed in the order that they appear in the list.