Run/Debug Configuration: MPS Instance
This run/debug configuration allows running a new MPS instance from within another MPS instance and thus debug it or see it working on an arbitrary project.
Click here for the description of the options that are common for all run/debug configurations.
|MPS system path||The location to store the MPS system data, defaults to the location used by the current MPS instance|
|MPS configuration path||The location to store the MPS configuration data, defaults to the location used by the current MPS instance|
|Virtual machine parameters||provide command-line arguments to the JVM|
|Alternative JRE path||Explicitly specify a JRE distribution to use for running the class|
|Open current project||Indicate whether the new MPS instance shall open the project that is open in the current MPS instance|
|Project to open||Specify a project to open in the newly started MPS instance|
|Plugins to deploy||Choose plugins to make available in the newly started MPS instance|
|N/A||Click this button to add a new configuration to the list.|
|N/A||Click this button to remove the selected configuration from the list.|
|N/A||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 newly created configurations.|
|or||N/A or N/A||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.
|Sort configurations||Click this button to sort configurations in alphabetical order.|
|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.|
|Share|| 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
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, MPS 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.
|Before launch||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. |