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 Style Sheet file. Type the path manually or click Browse 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 Style Sheet via the File Associations functionality. To specify a file, which is not on the list, click Browse and select the desired file in the Choose XML File dialog box, that opens.
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 Browse 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 checkbox 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 checkbox to have the file with the output opened in the configured Web browser after the script is executed successfully.
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.
In this tab, configure additional options that are not commonly required in run configurations.
Smart Error Handling
Clear this checkbox to have the console display full error messages including their complete stack traces, when an error occurs during execution.
Select this checkbox to suppress showing staktraces and have the console display only the relevant information about errors.
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.
In this text box, specify the working directory to use. Type the path manually or click Browse 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.
Use JDK - select this option to choose the JDK without including anything module- or project-related into the classpath.
When you edit a run configuration (but not a run configuration template), you can specify the following options for it:
In this text box, 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 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, 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.
Single instance only
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.
To create a folder, select the configurations within a category, click , and specify 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.
Under the Templates node in the tree view of run configurations, you can select a run configuration template and edit its default settings. This will not affect the configurations that are already created, but will be used as defaults when creating new configurations of the corresponding type.
When you select the Templates node itself, you will be able to adjust general settings that apply to all run/debug configurations:
Configurations available in Run Dashboard
In this section you can create a list of run configurations available in the Run Dashboard — a tool window that helps you execute and manage multiple run/debug configurations.
Note that the dashboard will only display the configuration types for which you have created one ore more configurations. Thus, if you add a configuration type for which no configurations exist in the project, this type will not be displayed on the dashboard until you create a configuration of this type.
Confirm rerun with process termination
The behavior of this checkbox depends on whether the Single instance only option is selected for a particular run/debug configuration.
If this checkbox is selected, in case of a single instance, launching a new process (for example, by clicking on the main toolbar) while another process is still running, results in showing a dialog box prompting to terminate the current process before launching a new one.
If this checkbox is not selected (or in case of multiple instances), IntelliJ IDEA starts the new process silently.
Temporary configurations limit
Specify the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.
Before Launch options
In this area you can specify tasks that must be 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:
Run External tool: select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in IntelliJ IDEA yet, add its definition. For more information, see Configuring Third-Party Tools and External Tools.
Run Another Configuration: select to execute another run/debug configuration. In the dialog that opens, select the configuration to be run.
If an error occurs during compilation, IntelliJ IDEA won't attempt to start the run/debug configuration.
Build, no error check: the same as the Build option, but IntelliJ IDEA will try to start the run/debug configuration irrespective of the compilation results.
Build Artifacts: select this option to build an artifact or artifacts. In the dialog that opens, select the artifact or artifacts that should be built.
Run Ant target: select this option to run an Ant target. In the dialog that opens, select the target to be run.
Run Grunt task: select this option to run a Grunt task. In the Grunt task dialog box that opens, specify the Gruntfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Grunt tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the grunt-cli package.
Run Gulp task: select this option to run a Gulp task. In the Gulp task dialog box that opens, specify the Gulpfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Gulp tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the gulp package.
Run Maven Goal: select this option to run a Maven goal. In the dialog that opens, select the goal to be run.
Start React Native Bundler: select this option to run the bundler automatically, as part of a running or debugging session. by default, this is done through react-native start. If your application uses Expo, you need to run the development server via the start npm task. To do that, click , then in the Configure React Native dialog, choose npm script and select start from the list.
If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start.
If the Check errors checkbox is cleared, the compiler will show all the detected errors but the run configuration still will be launched.
Generate CoffeeScript Source Maps: select this option to generate the source maps for your CoffeeScript sources. In the dialog that opens, specify where your CoffeeScript source files are located.
Upload files to Remote Host: select this option to have the application files automatically uploaded to the server according to the default server access configuration.