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.
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, AppCode 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.
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 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.
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 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.
Click this button to add a new configuration to the list.
Click this button to remove the selected configuration from the list.
Click this button to create a copy of the selected configuration.
Click this button to edit the default configuration templates.
The defaults are used for newly created configurations.
⌥↑ or ⌥↓
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.
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
Click this button to sort configurations in alphabetical order.
In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.
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.
Select this check box to make the run/debug configuration available to other team members.
The shared run/debug configurations are kept in separate xml files under .idea\runConfigurations folder,
while the local run/debug configurations are kept in
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, AppCode 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.
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.
Click this icon to add a task to the list. Select the task to be added:
Run External tool.
Select this option to run an application which is external to AppCode.
In the dialog that opens, select the application or applications that should be run.
If the necessary application is not defined in AppCode yet, add its definition.
For more information, see Configuring Third-Party Tools and External Tools.
Run Another Configuration.
Select this option to have another run/debug configuration executed.
In the dialog that opens, select the configuration to run.
This option is available only if you have already at least one run/debug configuration in the current project.
Run File Watchers.
Select this option to have AppCode apply all the currently active file watchers,
see Using File Watchers for details.
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 Grunt 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 npm Script. Select this check box to execute an npm script.
In the NPM Script dialog box that opens, specify the package.json file where the required script is defined,
select the script to execute, choose the command to apply to it, and specify the arguments to execute the script with.
Specify the location of the Node.js interpreter and the parameters to pass to it.
Compile TypeScript. Select this option to run the built-in TypeScript compiler
and thus make sure that
In the TypeScript Compile Settings dialog that opens, select or clear the Check errors check box
to configure the behaviour of the compiler in case any errors are detected:
If the Check errors check box is selected, the compiler will show all the errors
and the run configuration will not start.
If the Check errors check box is cleared, the compiler will show all the detected errors
but the run configuration still will be launched.