Run/Debug Configuration: OSGi Bundles

Bundles tab

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.

Item	Description
Bundles Name	This read-only field shows the names of the OSGi bundles to be installed.
Start Level	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. Note 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. Tip This functionality is presently available for the Equinox framework only.

Parameters tab

In these tab, customize the framework run or debug procedure by specifying additional parameters.

Item	Description
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, click and type the desired string in the VM Options dialog. When specifying the 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 the spaces in double quotes, for example, some" "arg or "some arg". If an option includes double quotes (e.g. as part of the argument), escape the double quotes by means of the backslashes, for example, -Dmy.prop=\"quoted_value\". Note 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.
Runtime Directories	In this area, specify the runtime working directory and the framework directory. Osmorc Controlled - select this option to have the default settings used. User Defined - select this option to specify the runtime directories of your choice manually. Working Directory - in this text box, specify the directory to start the framework from. Type the path to the desired folder manually or click the Browse button and choose the folder in the dialog that opens. Framework Directory - in this text box, specify the directory to have configuration files, bundles, and their run-time states stored in. Type the path to the desired folder manually or click the Browse button and choose the folder in the dialog that opens.

Additional framework properties

Item	Description
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.

Toolbar

Item	Shortcut	Description
	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.

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.

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.

Item	Keyboard shortcut	Description
	Alt+InsertCommand N; Command Enter	Click this button to add one of the tasks to be executed prior to launching the application. The possible tasks are: Run External tool: Add this task to have IntelliJ IDEA launch the specified third-party tool prior to running or debugging. To appoint a tool to launch, select it in the External Tools dialog box that opens. Make: Add this task to compile the project automatically, prior to running or debugging. This option helps you ensure that all changes are included and compiled. If there are no changes, the program will just run. Build Artifacts: Add this task to build the specified artifacts prior to running or debugging. To define the artifacts to be built, click the Browse button and select the desired artifact from the list of artifacts configured for the current module. To learn more about configuring artifacts, refer to Artifacts section. Run Another Configuration: Add this task to choose one of the already defined temporary or permanent run/debug configurations. Run Ant target:Add this task to build the specified Ant target prior to running or debugging. To define an Ant target, click Browse button and select the desired target from the list of existing targets. To learn more about Ant support, refer to Ant Support section. Run Maven goal: Add this task to execute the specified Maven goal prior to running or debugging. To define a Maven goal to be executed, click Browse button and select the desired goal from the list. To learn more about Maven support, refer to Maven Support section.
	Alt+DeleteCommand Delete	Click this button to remove selected task from the list.
	EnterEnter	Click this button to open the selected task for editing.
or	Alt+UpCommand Up or Alt+DownCommand Down	Click these buttons to move the selected task one line up or down. Note that Before launch actions are performed in the order they are specified in the run/debug configuration dialog.
Show this page		Select this check box to always show the Edit Run/Debug Configuration dialog prior to launching the current run/debug configuration. If this check box is not selected, run/debug configuration will be launched silently.

IntelliJ IDEA 12.1.0 Web Help