Difference between revisions of "Export Your OSGi Bundle"
(→Export Your OSGi Bundle) |
(→Export Your OSGi Bundle) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Export Your OSGi Bundle == | == Export Your OSGi Bundle == | ||
In this example, you'll export an OSGi bundle (as a JAR file) into a directory on your local file system. This bundle could then be installed and run in any OSGi-enabled container. | In this example, you'll export an OSGi bundle (as a JAR file) into a directory on your local file system. This bundle could then be installed and run in any OSGi-enabled container. | ||
| + | |||
| + | NOTE: Yes, OSGi bundles are just JAR files. This means they can be used in the same way as any other JAR file. However, if an OSGi bundle (JAR) is deployed onto a non-OSGi enabled container, the OSGi meta data (inside MANIFEST.MF) will simply be ignored. | ||
First, start with the OSGi project you wish to bundle. | First, start with the OSGi project you wish to bundle. | ||
| Line 6: | Line 8: | ||
Check the manifest by viewing it in your editor. | Check the manifest by viewing it in your editor. | ||
[[Image:bundle-2.png|left|thumb]]<br style="clear:left;" /> | [[Image:bundle-2.png|left|thumb]]<br style="clear:left;" /> | ||
| − | + | Right click, then select Run As -> Run Configurations ... | |
[[Image:bundle-3.png|left|thumb]]<br style="clear:left;" /> | [[Image:bundle-3.png|left|thumb]]<br style="clear:left;" /> | ||
Give your configuration a name, and deselect Target Platform - leaving only your project. Now click Apply followed by Run. | Give your configuration a name, and deselect Target Platform - leaving only your project. Now click Apply followed by Run. | ||
Latest revision as of 13:56, 30 January 2011
Export Your OSGi Bundle
In this example, you'll export an OSGi bundle (as a JAR file) into a directory on your local file system. This bundle could then be installed and run in any OSGi-enabled container.
NOTE: Yes, OSGi bundles are just JAR files. This means they can be used in the same way as any other JAR file. However, if an OSGi bundle (JAR) is deployed onto a non-OSGi enabled container, the OSGi meta data (inside MANIFEST.MF) will simply be ignored.
First, start with the OSGi project you wish to bundle.
Check the manifest by viewing it in your editor.
Right click, then select Run As -> Run Configurations ...
Give your configuration a name, and deselect Target Platform - leaving only your project. Now click Apply followed by Run.
In the Console window you can see your bundle running.
Type 'ss' inside the Console window to see the ID of your bundle.
Use the 'stop' command to stop your bundle. Then click the red square just above the Console window to stop the execution environment.
Now click on the File menu and select Export.
Select Plug-in Development -> Deployable plug-ins and fragments.
Select the project to export and give the directory name on your local file system that will hold your OSGi bundle. Then check the Options tab.
Uncheck Export Source (if necessary) and then click Finish.
Open a terminal window and verify that your bundle was saved.
Congratulations! You've just exported your OSGi bundle onto your local file system.
