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 - 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, AppCode 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 to expand the textbox and type the text there.
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.
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Specify a name for the run/debug configuration to quickly identify it when editing or running the configuration, for example, from the Run popup ⌥ ⇧ F10.
Allow parallel run
Select to allow running multiple instances of this run configuration in parallel.
By default, it is disabled, and when you start this configuration while another instance is still running, AppCode suggests to stop the running instance and start another one. This is helpful when a run/debug configuration consumes a lot of resources and there is no good reason to run multiple instances.
Store as project file
Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project.
By default, it is disabled, and AppCode stores run configuration settings in .idea/workspace.xml.
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 button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.
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.
In this area, you can specify tasks to 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 AppCode yet, add its definition. For more information, see External 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.
Run Grunt task: select this option to run a Grunt task.
In the Grunt task dialog 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 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 option to execute an npm script.
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.
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
By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration.
Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing ⌥ 4 or ⌥ 5.