Run/Debug Configuration: Grails
Grails run/debug configuration enables you to run and debug the Grails applications, tests and Web tests.
The dialog 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, |
Alternatively, you can execute target as described in the section Run 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 |
When specifying JVM options, follow these rules:
|Environment Variables||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
|Launch browser||By default, this checkbox is not selected and IntelliJ IDEA uses http://localhost:8080/application_name as default address. Select this checkbox to enter a different address in the field.|
Code Coverage tab
Use this tab to configure code coverage monitoring options.
|Choose 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 checkbox to detect lines covered by one test and all tests covering line. If this checkbox is selected, becomes available on the toolbar of the coverage statistic popup.
Refer to the section Set coverage in run configurations.
|Packages and classes to record code coverage data||Click and select Add Class or Add Package 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 checkbox 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.
|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 |
|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
For more information, see parallel builds in Maven 3 feature.
|Maven home directory||Use this 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.|
|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.|
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Specify a name for the run/debug configuration to quickly identify it when editing or running the configuration, for example, from the Run popup Alt+Shift+F10.
|Allow parallel run|
Select to allow running multiple instances of this run configuration in parallel.
By default, it is disabled, and when you start this configuration while another instance is still running, IntelliJ IDEA suggests to stop the running instance and start another one. This is helpful when a run/debug configuration consumes a lot of resources and there is no good reason to run multiple instances.
|Store as project file|
Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project.
By default, it is disabled, and IntelliJ IDEA stores run configuration settings in .idea/workspace.xml.
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.
|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.|
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.|
In this area, you can specify tasks to 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:
|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|
Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5.