Run/Debug Configuration: Java Scratch

The Java Scratch run/debug configuration enables you running or debugging Java scratch files that have the main() method.

Click here for the description of the options that are common for all run/debug configurations.

Item	Description
Main class	In this text box, specify the fully qualified name of the class to be executed (passed to the JRE). Type the class name manually or click Browse to open the Choose Main Class dialog box, where you can find the desired class by name or search through the project.
Path to scratch file	Specify here the path to the scratch file, or select one from the file chooser.
VM options	In this text box, specify the string to be passed to the VM for launching an application, for example, `-mx`, `-verbose`, and so on. If necessary, click and type the desired string in the VM Options dialog. When specifying JVM options, follow these rules: Use spaces to separate individual options, for example, `-client -ea -Xmx1024m`. If an option includes spaces, enclose the spaces or the argument that contains spaces in double quotes, for example, `some" "arg` or `"some arg"`. If an option includes double quotes (as part of the argument), escape the double quotes using backslashes, for example, `-Dmy.prop=\"quoted_value\"`. You can pass environment variable values to custom Java properties. For example, if you define a variable `MY_ENV_VAR`, you can pass it to the `foo` property as follows: `-Dfoo=${MY_ENV_VAR}` The `-classpath` option specified in this field overrides the classpath of the module.
Program arguments	In this text box, type a list of arguments to be passed to the program in the format you would use in the command line. If necessary, click the button and type the desired arguments in the Program Parameters dialog box. Use the same rules as for specifying the VM options.
Working directory	In this text box, specify the current directory to be used by the running application. This directory is the starting point for all relative input and output paths. By default, the field contains the directory where the project file resides. To specify another directory, click the Browse button select the directory in the dialog that opens. Click the icon to view the list of available path variables that you can use as a path to your working directory. The list of the path variables may vary depending on the enabled plugins.
Environment variables	Click Browse to open the Environment Variables dialog box, where you can create variables and specify their values. Note that you can copy-paste the contents of the Environment variables field without having to open the Environment Variables dialog box.
Use classpath of module	Select the module whose classpath should be used to run the application.
Include dependencies with 'Provided' scope	Enable this option to add dependencies with the Provided scope to the runtime classpath.
Shorten command line	Select a method that will be used to shorten the command line if the classpath gets too long or you have many VM arguments that exceed your OS command line length limitation: none: IntelliJ IDEA will not shorten a long classpath. If the command line exceeds the OS limitation, IntelliJ IDEA will be unable to run your application and will display a message suggesting you to specify the shortening method. JAR manifest: IntelliJ IDEA will pass a long classpath via a temporary `classpath.jar`. The original classpath is defined in the `manifest` file as a `class-path` attribute in `classpath.jar`. Note that you will be able to preview the full command line if it was shortened using this method, not just the classpath of the temporary `classpath.jar`. classpath.file: IntelliJ IDEA will write a long classpath into a text file. User-local default: this legacy option is set automatically for projects created before IntelliJ IDEA version 2017.3. IntelliJ IDEA will configure this setting depending on the properties set in the `ide/workspace.xml` and `idea.config.path/options/options.xml` files.
JRE	By default, the project JDK is used to run the application. If you want to specify an alternative JDK or JRE here, select it from the drop-down list.
Enable capturing form snapshots	Select this check box to enable the GUI Designer to take snapshots of the GUI components, that can be afterwards converted into a form.

Toolbar

Item	Shortcut	Description
	`Alt+Insert`	Click this button to add a new configuration to the list.
	`Alt+Delete`	Click this button to remove the selected configuration from the list.
	`Ctrl+D`	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	`Alt+Up` or `Alt+Down`	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.
	Move into new folder / Create new folder	Use this button to create a new folder. 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 buttons.
	Sort configurations	Click this button to sort configurations in alphabetical order.

Common options

Item Description

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.

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.

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, IntelliJ IDEA 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.

Item	Keyboard shortcut	Description
	`Alt+Insert`	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 IntelliJ IDEA. In the dialog that opens, select the application or applications that should be run. If the necessary application is not defined in IntelliJ IDEA yet, add its definition. For more information, see Configuring Third-Party Tools and External Tools. Build Artifacts. Select this option to have an artifact or artifacts built. In the dialog that opens, select the artifact or artifacts that should be built. See also Working with Artifacts. 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 Ant target. Select this option to have an Ant target run. In the dialog that opens, select the target to be run. For more information, see Ant. 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 option to execute an npm script. In the NPM Script dialog box that opens, specify the npm run/debug configuration settings. Compile TypeScript. Select this option to run the built-in TypeScript compiler and thus make sure that all the changes you made to your TypeScript code are reflected in the generated JavaScript files. In the TypeScript Compile Settings dialog that opens, select or clear the Check errors checkbox to configure the behaviour of the compiler in case any errors are detected: 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 have the source maps for your CoffeeScript sources generated. In the dialog that opens, specify where your CoffeeScript source files are located. Run Maven Goal. Select this option to have a a href="Maven_Support.xml">Maven goal runRun/Debug Configuration: Java Scratch. In the dialog that opens, select the goal to be run. Run Remote External tool: Add a remote SSH external tool. Refer to the section Remote SSH External Tools for details. Run Rake task:Add a Rake task to be executed prior to running or debugging. To choose a Rake task, click the browse button , and select the desired task from the list of available tasks. Note that code completion is available here. To learn more about Rake support, refer to Rake Support section. Run JRuby compiler: choose this option to execute JRuby compiler with the specified target path, compiler process heap size, and command line parameters (if any).
	`Alt+Delete`	Click this icon to remove the selected task from the list.
	`Enter`	Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
	`Alt+Up`	Click this icon to move the selected task one line up in the list.
	`Alt+Down`	Click this icon to move the selected task one line down in the list.
Show this page		Select this check box to have the run/debug configuration settings shown prior to actually starting the run/debug configuration.
Activate tool window		Select this option if you want the Run/Debug tool windows to be activated automatically when you run/debug your application. This option is enabled by default.

Last modified: 24 July 2018

Procedures:

Concepts:

Working with Run/Debug Configurations

IntelliJ IDEA 2018.1 Help