|Module||From this drop-down list, select the IntelliJ IDEA module to apply this configuration to.|
|GWT Module to Load||From this drop-down list, select the GWT module to deploy.|
|VM options||In this text box, specify the string to be passed to the VM.
Usually this string contains the options such as -mx, -verbose, etc.
Type the arguments right in the text box or in the VM Options dialog that opens when you click .
When specifying the options, follow these rules:
|Dev Mode parameters||
In this text box, specify the parameters for the GWT development mode.
Type the parameters right in the text box or in the GWT Dev Mode Parameters dialog that opens
when you click .
Use the same rules as for specifying the VM options.
From this drop-down list, select the name of the .html file
that implements the starting page of the application.
This drop-down is still available even if you clear the Open in browser check box to run the application in the embedded GWT development mode without launching the browser.
|Open in browser||
Select this check box to have IntelliJ IDEA launch the browser and show the application implemented in the specified GWT module.
From the drop-down list, choose the browser to open. The preselected Default value
means that the browser specified as default at the IntelliJ IDEA will be launched.
Contrary to previous IntelliJ IDEA versions, where this functionality was implemented through integration with the native GWT Development Mode window, now you can choose yourself whether to have the application opened in the browser or not.
|Update resources on frame deactivation||Select this check box to have all the application resources (that is, all the application components except classes) updated when IntelliJ IDEA loses the focus.|
|InsertInsert||Click this button to add new configuration to the list.|
|DeleteDelete||Click this button to remove the selected configuration from the list.|
|Ctrl+DCtrl+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+UpCommand Up or Alt+DownCommand 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 0 are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created.
|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||In this area, specify the actions to be performed prior to executing the current run/debug configuration.