Community
Participate
Working Groups
When using Eclipse to develop OSGi bundles you quite often need to "osgify" external libraries. To do this you can use "File -> New -> Project -> Plug-in Development -> Plug-in from existing JAR archives" When plug-in is created, the "Export-Package" entries in the generated MANIFEST do not hold any version attribute. According to OSGi R4 specs it means exported packages do have version "0.0.0" instead of having the same version as the Bundle-Version meta tag. Missing versioning from Export-Package and Import-Package meta tags is a common issue in OSGi development and specifying them is considered as a "best practice". It would be great if the "Plug-in from existing JAR archives" functionality would by default add version attribute to ""Export-Package" entries. The version value would be the same as the "Bundle-Version".
Created attachment 112707 [details] proposed patch it sounds fair here is a patch to implement this behaviour
Created attachment 112708 [details] mylyn/context/zip
Ben, we should only be doing this if ONE jar is selected, it doesn't make sense to do this if multiple jars are selected as the versions may conflict.
Created attachment 115499 [details] updated patch Ouch, I didn't see your comment Chris, sorry! I of course agree with your suggestion
done. > 20091019 Thanks Benjamin!