Run/Debug Configuration: GWT
From this drop-down list, select the IntelliJ IDEA module to apply this configuration to.
Use Super Dev Mode
Select this checkbox to use GWT Super Dev Mode. In this case you can quickly recompile your code and check the output in a browser.
GWT Modules to Load
From this drop-down list, select the GWT module to deploy.
|In this text box, specify the string to be passed to the VM. Usually this string contains the options such as |
Type the arguments right in the text box or in the VM Options dialog that opens when you click .
When specifying JVM 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.
|In this text box, specify the current directory to be used by the running test. This directory is the starting point for all relative input and output paths. By default, the field contains the directory where the project file resides. To specify another directory, click Browse select the directory in the dialog that opens. |
Click the icon to view the list of available environment variables that you can use as a path to your working directory. In this case you do not need to specify any additional environment variables in the Environment variables field.
Click Browse to open the Environment Variables dialog box, where you can create variables and specify their values.
Use this drop-down list to select a server for your application. IntelliJ IDEA uses Jetty Web server as a default one.
| 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 checkbox to run the application in the embedded GWT development mode without launching the browser.
By default, the project JDK is used to run the application. If you want to specify an alternative JDK or JRE here, select it from the drop-down list.
Open in browser
| Select this checkbox 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.
When you edit a run configuration (but not a run configuration template), you can specify the following options:
In this field, 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 checkbox 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, or 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 otherwise.
Allow running in parallel
When disabled, 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 checkbox is selected, it is possible to launch as many instances of the run/debug configuration as required. So doing, each runner will start in its own tab of the Run Tool Window or Debug Tool Window.
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 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-and-drop or and buttons.
To remove grouping, select a folder and click .
Click this button to sort configurations in the alphabetical order.
Before Launch options
In this area you can specify tasks that must 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, if the checkbox is cleared, 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.