Run/Debug Configuration: OSGi Bundles
Use this dialog box to set up options for running and debugging applications that use OSGi Bundles.
The dialog box consists of the following tabs:
Click here for the description of the options that are common for all run/debug configurations.
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.
|OSGi Framework||From a drop-down 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.|
|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. |
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 checkbox 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.|
In these tab, customize the framework run or debug procedure by specifying additional parameters.
|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 JVM options, follow these rules:
|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.
|JRE||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 drop-down list.|
|Runtime Directory||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
|Debug Mode||Select this checkbox 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 |
|Start OSGi Console|| Select this checkbox to run a prompt for the specified framework. For example, for the Equinox framework it is |
|Run||Use this area to indicate what target you need to run.|
You can select from the following options:
|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.|
|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.|
|Share|| 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
If the file-based format is used, the settings are stored in the
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. |