IntelliJ IDEA 12.1.0 Web Help

10.1.1+
Some features described here are available in Ultimate edition only.

Use this dialog to create or edit run/debug configurations for Google App Engine Development Server.

Name field and Share option

ItemDescription
NameUse this field to edit the name of the run/debug configuration.

This field is not available when editing the run/debug configuration defaults.

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 .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.

Server Tab

ItemDescription
Application ServerSelect the server configuration to be used.

Click Configure to create a new server configuration or edit an existing one. (The Application Servers dialog will open.)

Start browserSelect this check box to run the default Web browser to study your application output there.
With JavaScript DebuggerIf this check box is selected, the Web browser is started with the JavaScript debugger enabled.

Note

JavaScript debugging is available for Firefox only. Note that when you debug your JavaScript in Firefox for the first time, the JetBrains Firefox extension will be installed.

Startup pageIn this field, specify the URL the browser should go to when started. In most typical cases, this URL will correspond to the root of your Web application or its starting page.
VM optionsIf necessary, specify the command-line options to be passed to the server JVM at the server start.

If you need more room to type, click shift-enter-button next to the field to open the VM Options dialog where the text entry area is larger.

When specifying the options, follow these rules:

  • Use spaces to separate individual options, for example, -client -ea -Xmx1024m.
  • If an option includes spaces, enclose the spaces or the argument that contains the spaces in double quotes, for example, some" "arg or "some arg".
  • If an option includes double quotes (e.g. as part of the argument), escape the double quotes by means of the backslashes, for example, -Dmy.prop=\"quoted_value\".
Perform on 'Update' action Select the necessary option for the Update application action.

The available options are:

  • Update resources. All changed resources (that is, all application components other than the classes) will be updated.
  • Update classes and resources. All changed resources will be updated; changed classes will be recompiled.

    In the debug mode, the updated classes will be hot-swapped. In the run mode, IntelliJ IDEA will just update the changed classes in the output folder. Whether such classes will actually be reloaded in the running application, depends on the capabilities of the runtime being used.

  • Restart server. The server will be restarted. The updated version of the application will be deployed at the server startup.
Show dialog Select this check box if you want to see the Update <application name> dialog every time you perform the Update application action.

The Update <application name> dialog is used to view and change the current update option prior to actually updating the application.

On frame deactivation Specify which application update actions should be performed when switching from IntelliJ IDEA to a different application (for example, a Web browser). (Frame deactivation means switching to a different application.)

If no update actions are required, select Do nothing. Otherwise, select the necessary update option. Note that the Restart server option is not available.

Web Artifact to deploySelect the artifact to be deployed on the server.
PortSpecify the server HTTP port.
Server parametersIf necessary, specify the command-line arguments to be passed to the server.

Logs tab

Use this tab to specify which log files generated while running or debugging should be displayed in the console, that is, on the dedicated tabs of the Run or Debug tool window.

ItemDescription
Is ActiveSelect check boxes in this column to have the log entries displayed in the corresponding tabs in the Run tool window or Debug tool window.
Log File EntryThe read-only fields in this column list the log files to show. The list can contain:
  • Full paths to specific files.
  • Ant patterns that define the range of files to be displayed.
  • Aliases to substitute for full paths or patterns. These aliases are also displayed in the headers of the tabs where the corresponding log files are shown.

    Note

    If a log entry pattern defines more than one file, the tab header shows the name of the file instead of the log entry alias.

Skip ContentSelect this check box to have the previous content of the selected log skipped.
Save console output to fileSelect this check box to save the console output to the specified location. Type the path manually, or click the browse button and point to the desired location in the dialog that opens.
Show console when standard out changesSelect this check box to activate output console and bring it forward, if associated process writes to Standard.out.
Show console when standard error changesSelect this check box to activate output console and bring it forward, if associated process writes to Standard.err.
add Click this button to open the Edit Log Files Aliases dialog where you can select a new log entry and specify an alias for it.
edit1Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog.
deleteClick this button to remove the selected log entry from the list.
browseButton.png Click this button to edit the select log file entry.

Note

The button is available only when an entry is selected.

Code Coverage tab

Use this tab to configure code coverage monitoring options.

Note that this tab is not available for remote servers.

ItemDescription
Choose code coverage runnerSelect the desired code coverage runner.
SamplingSelect this option to measure code coverage with minimal slow-down.
TracingSelect this option to collect accurate branch coverage. This mode is available for the IntelliJ IDEA code coverage runner only.
Track per test coverageSelect this check box to detect lines covered by one test and all tests covering line.
Packages and classes to record code coverage dataIf necessary, specify the classes and packages to be measured.

Use add-class or add-package to add classes or packages to the list.

To remove the classes or packages from the list, select the corresponding list items and click delete.

Enable coverage in test folders.Select this check box to include the test source folders in code coverage analysis.

Before Launch options

ItemDescription
Before Launch Specify which activities should be performed before starting the run/debug configuration:
  • Make. If this check box is selected, the project is compiled automatically prior to running or debugging. This option helps you ensure that all changes are included and compiled.
  • Build Artifacts. If this check box is selected, the specified artifacts will be built prior to running or debugging. To define the artifacts to be built, click browseButton and select the desired artifacts.
  • Run Ant target. If this check box is selected, the specified Ant target will be built prior to running or debugging. To define the Ant target, click browseButton and select the desired target.

    To learn more about Ant support, refer to the Ant Support section.

  • Run Maven goal. If this check box is selected, the specified Maven goal will be executed prior to running or debugging. To define the Maven goal to be executed, click browseButton and select the desired goal.

    To learn more about Maven support, refer to the Maven Support section.

  • Show this page. Select this check box if you want the Run/Debug Configurations dialog to be shown every time you launch this run/debug configuration.

Note

The Before Launch actions are performed in the order they appear in the Run/Debug Configurations dialog.

Toolbar

ItemDescription
add (InsertInsert)Use this icon or shortcut to create a new run/debug configuration.
delete (DeleteDelete)Use this icon or shortcut to delete the selected run/debug configuration.
copy (Ctrl+DCtrl+D)Use this icon or shortcut to create a copy of the selected run/debug configuration.
settings Click this button to edit the default settings for run/debug configurations.
arrowUp arrowDownUse these buttons to 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 in the corresponding list on the main toolbar.

See Also

Concepts:

Procedures:

Web Resources: