Grails run/debug configuration enables you to run and debug the Grails applications, tests and Web tests.
The dialog box consists of the following tabs:
|Module||Select application, for which this run/debug configuration is created. By default, the name of the current module is suggested.|
|Command line||Type a command to execute a particular target, for example, run-app,
Alternatively, you can execute target as described in the section Running Grails Targets.
|VM Options||Specify the string to be passed to the VM for launching the application.
This string may contain the options such as -mx, -verbose, etc.
When specifying the options, follow these rules:
|Environment Variables||Click the Browse button to open the Environment Variables dialog box, where you can create variables and specify their values.|
If this check box is selected, it means that the user intends to include the dependency directly, by passing --classpath to the command line.
|Launch browser||Select this check box to open the default browser.|
Code Coverage tab
Use this tab to configure code coverage monitoring options.
|Choose code coverage runner||Select the desired code coverage runner.|
|Sampling||Select this option to measure code coverage with minimal slow-down.|
|Tracing||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. If this check box
is selected, becomes available on the toolbar of the coverage statistic pop-up window.
This option is only available for the Tracing mode of code coverage measurement for the testing run/debug configurations.
Refer to the section Viewing Code Coverage Results.
|Merge data with previous results||When you run your unit testing or application configuration several times, use this item to calculate
statistics in the Project View, taking into account the
statistics of each time you have run the configuration.
Finally, the line is considered covered if it is covered at least once.
|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, the folders marked as test are included in the code coverage analysis.|
Maven settings tab
|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.|
|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.