[
https://issues.apache.org/jira/browse/GERONIMO-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated GERONIMO-3960:
--------------------------------------
Attachment: GERONIMO-3960.diff
Most of the work on this issue has already been done -- all the spec jars now
have the OSGi metadata.
There's only one remaining problem with the jars when using them in an OSGi
environment: they all import the packages they export. E.g. the EL 1.0 bundle
exports javax.el;version="1.0" but it also imports javax.el;version="1.0"
While this is a fine configuration for some bundles, there's no good reason for
the specs bundles to import their own packages. On top of that, the import
doesn't have an upper limit set on the version imported, which means that if
you install EL 2.2 in the same OSGi framewok instance as the EL 1.0 spec
mentioned before, it's perfectly possible that the import on the latter will
resolve to the packages exported by the former version (because 2.2 >= 1.0)
Attaching a patch that removes these imports by adding the
*{{-noimport:=true}}* flag to the Export-Packages configuration
> Make the spec jars OSGi friendly
> --------------------------------
>
> Key: GERONIMO-3960
> URL: https://issues.apache.org/jira/browse/GERONIMO-3960
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: specs
> Reporter: Guillaume Nodet
> Attachments: GERONIMO-3960.diff, stax-osgi.diff
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
