In this tab, compose a list of bundles to be installed, specify whether each bundle should be started upon installation, and define the order in which you want the bundles to be started.
|Bundles Name||This read-only field shows the names of the OSGi bundles to be installed.|
In this text box, specify the default start level for newly installed bundles and thus determine the start order of bundles.
The default value is 1.
An OSGi system has a current level (called the active start level). If a bundle has a start level higher than the active start level it will not start when the OSGi system starts. The bundle will start as soon as the active start level reaches or exceeds the start level of the bundle. Accordingly, if the active start level becomes below the level of a bundle, the bundle will be shutdown.
|Start After Install||Select this check box to have the selected bundle after installation.|
|Add||Click this button to open the Select Bundles dialog box, which displays all the currently available bundles. If the list is large, start typing the bundle name Search field - the contents of the list change as you type and show only the matching entries.|
|Remove||Click this button to delete the selected bundle from the list.|
|Framework Specific...||Click this button to select and add bundles that are specific for the current framework type.
This functionality is presently available for the Equinox framework only.
In these tab, customize the framework run or debug procedure by specifying additional parameters.
|OSGi Framework||From ths drop-down list, select the desired framework type. The list contains all the currently configured framework definitions.|
|VM Options||In this text box, specify the string to be passed to the Virtual Machine for launching the bundles.
If the string is too long and does not fit in the text box,
and type the desired string in the VM Options dialog.
When specifying the options, follow these rules:
The -classpath option specified in this field overrides the classpath of the module.
|Program Parameters||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 the string is too long and does not fit in the text box,
click the button
and type the desired arguments in the Program Parameters dialog box.
Use the same rules as for specifying the VM options.
|Use Alternative JRE||Select this check box to have the bundles run using a JRE which is different from the one used by the current project or module. Choose the location of the desired JRE from the drop-down list or click the Browse button and choose the folder in the Select Alternative JRE dialog box, that opens.|
|Include All Bundles in Class Path||Select this check box to have all the selected bundles included in the classpath.|
In this area, specify the runtime working directory and the framework directory.
Additional framework properties
|Debug Mode||Select this check box to enable debugging.|
|System Packages||In this text box, specify the system packages to be exposed inside the OSGi framework. Type the names of the packages using commas as separators. Wildcards are welcome.|
|Boot Delegation||In this text box, specify java packages for which the framework must delegate class loading to the boot class path. Type the names of the packages using commas as separators. Wildcards are welcome.|
|InsertInsert||Click this button to add new configuration to the list.|
|DeleteDelete||Click this button to remove the selected configuration from the list.|
|Ctrl+DCtrl+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 the newly created configurations.|
|or||Alt+UpCommand Up or Alt+DownCommand Down||Use these buttons to move the selected configuration or group of configurations (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.
|Use this button to create a new folder.
If one or more run/debug configurations have the focus, then the selected run/debug configurations 0 are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created.
|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.|
|Temporary configurations limit||Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.|
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 and 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 for the ones that are not shared.
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 make sense, when 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||In this area, specify the actions to be performed prior to executing the current run/debug configuration.