Running XSLT Scripts is as easy as opening the Editor Context Menu and either creating a permanent Run Configuration or simply choosing Run to instantly run the selected XSLT script.
Creating Run Configurations
Permanent Run Configurations can be created through Main Menu | Run | Edit Configurations. You'll find an additional tab named XSLT to add Run Configurations for XSLT scripts.
A Run Configuration can also be created by the Create "<name>" action from the context menu.
In that case, the name of the configuration will be taken from the stylesheet's file name and its path will already be filled into the XSLT script file text field. If the stylesheet defines parameters, those will be filled into the Parameters table with empty values. Parameters that are highlighted in blue don't have a value assigned yet and will not be passed to the stylesheet during execution, so it's not required to delete those automatically created parameter values if nothing should be passed to the stylesheet.
Run Configuration Settings
An XSLT Run Configuration has various settings that can be adjusted. The most important ones are the location of the XSLT script file and the XML input file that should be transformed. Those are mandatory and the specified files must exist, otherwise the configuration cannot be executed.
The XML input file combobox lists all XML files that have been associated with the chosen stylesheet via the File Associations functionality.
There are three different choices about how the output of the script should be handled. The first is
Show in default console. When this is selected, the output will appear 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
By default selected is the option Show in extra console tab which will show the output in an extra tab named XSLT Output. This option has the ability to highlight the produced output according to different file types that are available in CLion. However this is kind of an experimental feature, so it can be turned off completely by selecting the Disabled option. The output will then be written into a temp file that is displayed by the normal Log Viewer.
The last option, Save to file can be used to directly write the output to a file. The textfield must not be empty and can refer to any existing or non-existing file. Check the option Open file in editor after execution to open the file in CLion after the script ends normally. The option Open file in web browser can be checked to open the generated file in the configured web browser after execution has finished.
The Parameters table is used to specify the parameter names and their values that should be passed to the script. Press the Add and Remove buttons to modify the list. A newly added parameter will not have any value assigned by default, and thus will not be passed to the script if the value isn't edited.
This tab allows you to control some options that are not needed for usual run configurations.
Smart error handling
Uncheck this to see full error messages including their complete stack traces when an error occurs during execution. When checked, those stack traces will be suppressed and only the relevant information about errors will be displayed in the console.
Allows you to pass arbitrary VM arguments to the VM that is used for running the XSLT script.
The working directory to use. When left empty, the working directory will be the directory the XSLT script file is located in.
Classpath and JDK
Allows you to choose the environment to run the script under. The default setting is the Module the XSLT script file belongs to. The option From module will also include the full classpath of the chosen module. This can be needed if the script makes use of custom XSLT Extension Functions.
The option Use JDK allows to select 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.