Run/Debug Configuration: Groovy
This run/debug configuration is intended for the Groovy scripts.
|Script path||Type the path to the Groovy script to be launched, or click the ellipsis button and select one from the tree view.|
|Module||Select the module the run/debug configuration is created for. By default, the name of current module is suggested.|
|VM Options||Specify the string to be passed to the VM for launching the Groovy script. This string may contain the options such as |
When specifying the options, follow these rules:
|Script Parameters||Type the list of arguments to be passed to the Groovy Script, same way as if you were entering these parameters in the command line. |
Use the same rules as for specifying the VM options.
|Environment variables||Click the Browse button to open the Environment Variables dialog box, where you can create variables and specify their values.|
|Working directory||Specify the root directory for the files referenced in script.|
|Enable debug stacktrace||If this check box is selected, the detailed debug stacktrace is produced, including the Groovy method calls. This information can be helpful in case of exceptions.|
|Add module classpath to the runner||Select this check box to include a module classpath when you are running a Groovy script.|
|Alt+Insert||Click this button to add a new configuration to the list.|
|Alt+Delete||Click this button to remove the selected configuration from the list.|
|Ctrl+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 newly created configurations.|
|or||Alt+Up or Alt+Down||Use these buttons to move the selected configuration or 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.
|Move into new folder / Create new folder||Use this button to create a new folder. |
If one or more run/debug configurations are in focus, the selected run/debug configurations are automatically moved to the newly created folder. If only a category is in focus, an empty folder is created.
Move run/debug configurations to a folder using drag-and-drop, or the buttons.
|Sort configurations||Click this button to sort configurations in alphabetical order.|
|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.|
|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
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 makes sense when the 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 must be performed before applying the run/debug configuration. The specified tasks are performed in the order they appear in the list. |