In this text box, specify the name of the current run/debug configuration.
Choose this option to create a configuration profile for running an applet via an applet class.
Choose this option to create a configuration profile for running an applet via a Web page.
Use the controls in the area to specify the applet implementation class and the applet size.
Applet Class - in this text box, specify the fully qualified name of the applet class to run. Type the name manually or click the Browse button to open the Choose Applet Class dialog box and select the path there.
Width - in this text box, type the desired width of the applet.
Height - in this text box, type the desired height of the applet.
The area is available after the Applet Class option is chosen.
In this area, specify a set of applet parameters.
Add - click this button to add a new entry to the list.
Remove - click this button to delete the selected entry from the list.
Name - in this text bos, specify the name of the applet parameter.
Value - in this text bos, specify the parameter value.
This area is available after the Applet Class option is chosen.
In the URL/HTML File text box, specify the file to invoke the applet from. Type the path to the file manually or click Browse and select the file in the dialog that opens.
This area is available after the URL option is chosen.
In this text box, specify the location of tje appletviewer.policy file. Because this file is distributed with IntelliJ IDEA, the text box is by default filled in with the standard location. To specify another location, click Browse and choose the desired location in the dialog that opens.
VM Options for Applet Viewer
In this text box, specify the string to be passed to the VM for executing the applet viewer. Usually this string contains the options such as -mx, -verbose, etc.
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:
The -classpath option specified in this field overrides the classpath of the module.
Use Classpath and JDK of the Module
From this drop-down list, select one of the modules configured in your project. The classpath and JDK of this module will be used to run the applet with the current run configuration.
Use Alternative JRE
Select this checkbox to enable defining another JRE than the JRE used by the current project / module.
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.
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.
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.
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.
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.
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 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.
Make Select this option to have the project or module compiled. The Make Module command will be carried out if a particular module is specified in the run/debug configuration, and the Make Project command otherwise.
If an error occurs during the compilation, IntelliJ IDEA won't attempt to start the run/debug configuration.
Make, no error check. The same as the Make option but IntelliJ IDEA will try to start the run/debug configuration irrespective of the compilation result.
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.
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.
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: Applet. In the dialog that opens, select the goal to be run.