Run/Debug Configuration: CloudBees Server
The Tomcat instance embedded in CloudBees is used as a server. This Tomcat instance is included in the server client libraries. You can download those libraries using a quick fix provided right in the run configuration:
If the message Error: Client libraries were not downloaded is shown in the lower part of the dialog, click Fix.
| Select this checkbox to start a web browser after starting the server and deploying the artifacts. |
Select the browser from the list. Click (Shift+Enter) to configure your web browsers.
The field underneath After launch
Specify the URL the browser should go to when started. Most likely, the default http://localhost:8080 will do.
|If 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 next to the field to open the VM Options dialog where the text entry area is larger.
When specifying JVM options, follow these rules:
On 'Update' action
| Select the necessary option for the Update application function ( or N/A in the Run or Debug tool window). |
| Select this checkbox if you want to see the Update dialog every time you use the Update application function. |
The Update dialog is used to select the Update option prior to actually updating the application.
On frame deactivation
| Specify what IntelliJ IDEA should do when you switch from the IDE to a different application (for example, a web browser). (Frame deactivation means switching to a different application.) |
The options other than Do nothing have the same meanings as in the case of the Update action.
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.
The server HTTP port.
The server JNDI port.
Specify an artifact or an external resource to be deployed on the server. (An external resource means a deployable Web component such as a WAR file which is not represented by a project artifact.)
There should be exactly one item in the deployment list. "Exploded" artifacts cannot be used.
To add an item to the list, click and do one of the following:
To add an artifact, select Artifact and choose the desired artifact in the dialog that opens.
To add an external resource, select External Source and choose the location of the desired resource in the dialog that opens.
(Alt+Delete) removes the selected items from the list.
Log File Entry
The read-only fields in this column list the log files to show. The list can contain:
Select this checkbox to have the previous content of the selected log skipped.
Save console output to file
Select this checkbox 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 a message is printed to standard output stream
Select this checkbox to activate the output console and bring it forward if an associated process writes to Standard.out.
Show console when a message is printed to standard error stream
Select this checkbox to activate the output console and bring it forward if an associated process writes to Standard.err.
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.
Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog.
Click this button to remove the selected log entry from the list.
Code Coverage tab
Use this tab to configure code coverage monitoring options.
Note that this tab is not available for remote servers.
Choose code coverage runner
Select the desired code coverage runner.
Select this option to measure code coverage with minimal slow-down.
Select this option to collect accurate branch coverage. This mode is available for the IntelliJ IDEA code coverage runner only.
Track per test coverage
Select this checkbox to detect lines covered by one test and all tests covering line.
Packages and classes to record code coverage data
|If necessary, specify the classes and packages to be measured. |
Use or to add classes or packages to the list.
To remove the classes or packages from the list, select the corresponding list items and click .
Enable coverage in test folders.
Select this checkbox to include the test source folders in code coverage analysis.
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
If this checkbox is selected, it is possible to launch a run configuration multiple times in parallel instead of rerunning it. Each runner will start in its own tab of the Run Tool Window or Debug Tool Window.
When disabled, every time a new instance of the 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. If you click OK in the confirmation dialog, the first instance of the runner will be stopped, and the next one will take its place. This makes sense when launching two instances of run/debug configurations of the same type consumes too much of the CPU and memory resources..
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.
The toolbar shows this button only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.
View and edit the template (that is, the default settings) for the selected run/debug configuration. The templates are displayed under the Templates node and 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 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.