Run/Debug Configuration: XSLT

Settings Tab

Item	Description
Input	Use the controls in this area to specify the XML file to process and the script to be executed. XSLT Script File - in this text box, specify the path to the XSLT stylesheet file. Type the path manually or click the Browse button and select the desired file in the Choose XSLT File dialog box, that opens. Choose XML Input File - from this drop-down list, select the XML input file to be transformed. The list contains all the XML files that have been associated with the chosen stylesheet via the File Associations functionality. To specify a file, which is not on the list, click the Browse button and select the desired file in the Choose XML File dialog box, that opens.
Output	Use the controls in this area to configure handling of the script output. Show in Default Console - select this option to have the output displayed in the normal run console, together with any warnings and error messages from the XSLT transformer, as well as messages generated by the script, e.g. by xsl:message. Show in Extra Console Tab - select this option to have the produced output displayed in an extra, XSLT Output, tab. This option is selected by default. Highlight Output As - from this drop-down list, select the file type to highlight the output as. Save to File - select this option to have the output saved directly to a file. In the text box, specify the name of the target file. Type the path to the file manually or click the Browse button and select the desired file in the Choose Output File dialog box, that opens. If you type the name of a file that does not exist, IntelliJ IDEA will create a file and save the output to it. Open File in Editor After Execution - select this check box to have the file with the output opened in the editor after the script is executed successfully. Open File in Web Browser After Execution - select this check box to have the file with the output opened in the configured Web browser after the script is executed successfully. The specified file will be overwritten without requesting for confirmation.
Parameters	Use the controls in this area to create and manage a list of parameters to be passed to the script. Add () - click this button to create a new entry. Remove () - click this button to remove the selected entry from the list. Name - in this text box, specify the name of the parameter. Value - in this text box, specify the value of the parameter. The field is mandatory. Parameters without values are not passed to the script. Values are not assigned by default.

Advanced Tab

In this tab, configure additional options that are not commonly required in run configurations.

Item	Description
Smart Error Handling	Clear this check box to have the console display full error messages including their complete stack traces, when an error occurs during execution. Select this check box to suppress showing staktraces and have the console display only the relevant information about errors.
VM Arguments	In this text box, specify optional VM arguments to be passed to the VM where the XSLT script is executed. These can be heap size, garbage collection options, file encoding, etc. If the line of VM arguments is too long, click the button and and type the text in the VM Arguments dialog box, that opens.
Working Directory	In this text box, specify the working directory to use. Type the path manually or click the Browse button and select the desired folder in the Working Directory dialog box, that opens. If no folder is specified in text box, the working directory will be the one where the XSLT script file is located.
Classpath and JDK	In this area, specify the environment to run the script in. By default, it is the module the XSLT file belongs to. From Module - select this option to execute the script in a specific module. From this drop-down list, select the desired module. The full classpath to the selected module is included. This can be required if the script uses custom XSLT Extension Functions. Use JDK - select this option to choose the JDK without including anything module- or project-related into the classpath. It can be useful to explicitly choose a specific JDK to test the script with.

Toolbar

Item	Shortcut	Description
	Insert	Click this button to add new configuration to the list.
	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 the newly created configurations.
or	Alt+Up or Alt+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.

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.

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.

Item	Keyboard shortcut	Description
	Alt+Insert	Click this button to add one of the tasks to be executed prior to launching the application. The possible tasks are: Run External tool: Add this task to have IntelliJ IDEA launch the specified third-party tool prior to running or debugging. To appoint a tool to launch, select it in the External Tools dialog box that opens. Make: Add this task to compile the project automatically, prior to running or debugging. This option helps you ensure that all changes are included and compiled. If there are no changes, the program will just run. Build Artifacts: Add this task to build the specified artifacts prior to running or debugging. To define the artifacts to be built, click the Browse button and select the desired artifact from the list of artifacts configured for the current module. To learn more about configuring artifacts, refer to Artifacts section. Run Another Configuration: Add this task to choose one of the already defined temporary or permanent run/debug configurations. Run Ant target:Add this task to build the specified Ant target prior to running or debugging. To define an Ant target, click Browse button and select the desired target from the list of existing targets. To learn more about Ant support, refer to Ant Support section. Run Maven goal: Add this task to execute the specified Maven goal prior to running or debugging. To define a Maven goal to be executed, click Browse button and select the desired goal from the list. To learn more about Maven support, refer to Maven Support section.
	Alt+Delete	Click this button to remove selected task from the list.
	Enter	Click this button to open the selected task for editing.
or	Alt+Up or Alt+Down	Click these buttons to move the selected task one line up or down. Note that Before launch actions are performed in the order they are specified in the run/debug configuration dialog.
Show this page		Select this check box to always show the Edit Run/Debug Configuration dialog prior to launching the current run/debug configuration. If this check box is not selected, run/debug configuration will be launched silently.