Eclipse Community Forums: Eclipse Platform » Export-Package version when creating Plug-in from existing JAR archives

Home » Eclipse Projects » Eclipse Platform » Export-Package version when creating Plug-in from existing JAR archives

Export-Package version when creating Plug-in from existing JAR archives [message #331688]

Tue, 16 September 2008 10:41

Eclipse User

Hello,

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 metatag.

Missing versioning from Export-Package and Import-Package metatags is a
common issue in OSGi development and specifying them is considered as a
"best practice".

Don't you think the "Plug-in from existing JAR archives" functionnality
should by default add version attribute to ""Export-Package" entries ?

The version value would be the same as the "Bundle-Version"

Frederic

Re: Export-Package version when creating Plug-in from existing JAR archives [message #331691 is a reply to message #331688]

Tue, 16 September 2008 11:45

Eclipse User

Originally posted by: zx.code9.com

Frederic Conrotte wrote:
> Hello,
>
> 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 metatag.
>
> Missing versioning from Export-Package and Import-Package metatags is a
> common issue in OSGi development and specifying them is considered as a
> "best practice".
>
> Don't you think the "Plug-in from existing JAR archives" functionnality
> should by default add version attribute to ""Export-Package" entries ?
>
> The version value would be the same as the "Bundle-Version"

That sounds like a fair suggestions.

Do you mind filing bug against PDE?

https://bugs.eclipse.org/bugs/enter_bug.cgi?product=PDE

By the way, in 3.5M2, PDE added support for flagging missing version
numbers on exported packages, imported packages and require bundle
versions. That should help people if they want to make sure version
constraint information is included on their projects.

Cheers,

~ Chris

Re: Export-Package version when creating Plug-in from existing JAR archives [message #331695 is a reply to message #331691]

Tue, 16 September 2008 16:06

Eclipse User

>Chris Aniszczyk a écrit :
>
> Do you mind filing bug against PDE?
Done.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=247553

Though I tried to dig, I was unsure if such request was already in bugzilla.

> By the way, in 3.5M2, PDE added support for flagging missing version
> numbers on exported packages, imported packages and require bundle
> versions. That should help people if they want to make sure version
> constraint information is included on their projects.

Cool stuff. Thanks for the tip.

Fred

Previous Topic:	Replacing Editor Icons at workbench startup
Next Topic:	Editor and Outline view integration

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Apr 27 00:03:09 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter