Run/Debug Configuration: GWT
This feature is only supported in the Ultimate edition.
Shift+Alt+F10
This section provides descriptions of the configuration-specific items, as well as the toolbar and options that are common for all run/debug configurations.
Item | Description |
---|---|
Module | 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. |
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 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. |
Working directory | 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 the Browse button select the directory in the dialog that opens. Click this 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. The list of environment variables may vary depending on the enabled plugins. |
Environment variables | Click the Browse button to open the Environment Variables dialog box, where you can create variables and specify their values. |
Server | Use this drop-down list to select a server for your application. IntelliJ IDEA uses Jetty Web server as a default one. |
Start Page | 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. |
JRE | 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. |
with JavaScript debugger | Select this checkbox for IntelliJ IDEA to use a JavaScript debugger for your application. |
Toolbar
Item | Shortcut | Description |
---|---|---|
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. |
Common options
Item | Description | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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.
|