Run/Debug Configuration: OSGi Bundles
Use this dialog to set up options for running and debugging applications that use OSGi Bundles.
The dialog consists of the following tabs:
Framework & Bundles Tab
In this tab, select a framework that you need, 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.
From the list, choose your framework.
Framework Start Level
Use this field to define a state of the execution in which a framework exists. You can modify the start level of the framework. This start level is used for managing the order of OSGi bundles' execution. If the bundle has a start level grater than the one for the framework, then it will be executed first.
Default Start Level
This field shows the default start level of bundles. In this case, the bundles are added after the framework's execution has started. You can modify the default start level for bundles.
This read-only field shows the names of the OSGi bundles to be installed.
|In this field, specify the default start level for newly installed bundles and thus determine the start order of bundles. The default value is 1.|
Start After Install
Select this checkbox to have the selected bundle after installation.
Click this button to open the Select Bundles dialog, 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.
Click this button to delete the selected bundle from the list.
In these tab, customize the framework run or debug procedure by specifying additional parameters.
|In this field, 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 field, click and type the desired string in the VM Options dialog. |
When specifying JVM options, follow these rules:
|In this field, 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 field, click the button and type the desired arguments in the Program Parameters dialog. |
Use the same rules as for specifying the VM options.
By default, the project JDK is used to run the bundles. If you want to specify an alternative JDK or JRE here, select it from the list.
|Use this area to specify the runtime path of the framework. |
You can select from the following options:
Include All Bundles in Class Path
Select this checkbox to have all the selected bundles included in the classpath.
Additional Framework Properties
Select this checkbox to enable debugging.
In this field, specify the system packages to be exposed inside the OSGi framework. Type the names of the packages using commas as separators. Wildcards are welcome.
In this field, specify
Start OSGi Console
Select this checkbox to run a prompt for the specified framework. For example, for the Equinox framework it is
|Use this area to indicate what target you need to run.|
You can select from the following options:
When you edit a run configuration (but not a run configuration template), you can specify the following options:
In this field, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example, from the Run popup Shift+Alt+F10.
Share through VCS
Select this checkbox to put the run/debug configuration under version control and make it 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.
Allow running in parallel
If this checkbox is selected, it is possible to launch a run configuration multiple times in parallel instead of rerunning it. Each runner will start in its own tab of the Run Tool Window or Debug Tool Window.
When disabled, every time a new instance of the 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. If you click OK in the confirmation dialog, the first instance of the runner will be stopped, and the next one will take its place. This makes sense when launching two instances of run/debug configurations of the same type consumes too much of the CPU and memory resources..
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
Create a run/debug configuration.
Delete the selected run/debug configuration. Note that you cannot delete default configurations.
Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.
View and edit the template (that is, the default settings) for the selected run/debug configuration. The templates are displayed under the Templates node and used for newly created configurations.
Move the selected run/debug configuration up and down in the list.
The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration.
Default templates of run/debug configurations are always sorted alphabetically.
Move into new folder / Create new folder. You can group run/debug configurations by placing them into folders.
To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created.
Then, to move a configuration into a folder, between the folders or out of a folder, use drag or and buttons.
To remove grouping, select a folder and click .
Click this button to sort configurations in the alphabetical order.
In this area you can specify tasks that must be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Click this icon to add one of the following available tasks:
Click this icon to remove the selected task from the list.
Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
Click these icons to move the selected task one line up or down in the list. (The tasks are performed in the order that they appear in the list.)
Show this page
Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.
Activate tool window
Otherwise, if the checkbox is cleared, the tool window isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5.