Run/Debug Configuration: Grails
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:
Select application, for which this run/debug configuration is created. By default, the name of the current module is suggested.
|Type a command to execute a particular target, for example, |
Alternatively, you can execute target as described in the section Running Grails Targets.
|Specify the string to be passed to the VM for launching the application. This string may contain the options such as |
When specifying JVM options, follow these rules:
Click Browse to open the Environment Variables dialog box, where you can create variables and specify their values.
If this checkbox is selected, it means that the user intends to include the dependency directly, by passing
By default, this checkbox is not selected and IntelliJ IDEA uses
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. If this check box is selected, becomes available on the toolbar of the coverage statistic pop-up window.
Refer to the section : view JUnit tests that cover the line at caret. .
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
Use this tab to configure Maven settings for running and debugging your application. By default, the Use project settings checkbox is selected and IntelliJ IDEA uses the default settings specified in your project.
|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.
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.
Select the desired level of checksum matching while downloading artifacts. You can opt to fails downloading, when checksums do not match (
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: |
Use this field to set the
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
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.
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.
When you edit a run configuration (but not a run configuration template), you can specify the following options for it:
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).
| 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
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.
Create a run/debug configuration.
Delete the selected run/debug configuration. Note that you cannot delete default configurations.
Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
View and edit the default template for the selected run/debug configuration. The templates are used for newly created configurations.
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 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-and-drop or and buttons.
To remove grouping, select a folder and click .
Click this button to sort configurations in the alphabetical order.
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:
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.
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.
Click this icon to add one of the following available tasks:
Click this icon to remove the selected task from the list.
Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
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
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.