Installing a Bundle on OSGi
mToolkit offers several ways to install a bundle on a connected OSGi framework depending on whether you have it in the workspace (as a "raw" plugin project or as a JAR file) or it is located outside the workspace.
Installing a Bundle from the Workspace
You can install a bundle from the workspace on a connected OSGi framework if there is an active plugin project dedicated to the bundle or if the bundle is built in a JAR file.
To install a bundle from your Eclipse workspace, in one of the Eclipse navigation views (e.g. Package Explorer) right-click the plugin project node or the JAR file node and select the target framework from the Install to menu. If you are installing the bundle from a plugin project, the plugin project will be built and exported to a JAR file. Then, the JAR file will be transferred to the OSGi framework and installed. In case you are installing the bundle by using a ready JAR file, the file will be directly deployed on the framework.
On success, the installed bundle will appear under the Bundles node of the framework-specific tree. If the Autostart bundles on install option from mToolkit's preferences is not selected, then the bundles being installed will not be started automatically - you have to start them yourself.
Installing a Bundle from outside the Workspace
To install a bundle from the Frameworks view:
On success, the installed bundle will appear under the Bundles node of the device-specific tree.
Uninstalling a Bundle from an OSGi Runtime
To uninstall an installed bundle from the target OSGi framework, in the Frameworks view select the bundle from the framework's tree, right-click it and use Uninstall Bundle. To uninstall several bundles with a single operation, simply select all of them in the framework's tree before selecting Uninstall Bundle.
If the OSGi Runtime is configured with a list of system bundles providing vital system functionality, e.g. if it is emulated or is created with the help of the Image Builder, you are not allowed to uninstall such bundles – uninstalling one of them might lead to loss of important OSGi framework capabilities.