[
https://issues.apache.org/jira/browse/DERBY-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614071#comment-13614071
]
Rick Hillegas commented on DERBY-6069:
--------------------------------------
Thanks, Bryan. You probably know more about what needs to be done for OSGi
annotations. I see that you listed some references on DERBY-4120.
I agree that we don't want to expose more than we have to. And it seems that
we're already doing that because we export whole packages rather than just the
classes which appear in the public api. I believe that there is a way to limit
the export to a subset of classes in a package. That could be the way we work
around the split package issue involving derby.jar and derbyclient.jar.
I agree that it would be good if we could find an OSGi expert to advise us. I'm
wary about relying on anecdotal references churned up by googling. Thanks.
> Derby doesn't export the version number in its OSGI exported packages
> ---------------------------------------------------------------------
>
> Key: DERBY-6069
> URL: https://issues.apache.org/jira/browse/DERBY-6069
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.9.1.0, 10.8.3.0
> Reporter: Christian Müller
> Labels: osgi
> Attachments: MANIFEST.MF
>
>
> Derby doesn't export the version number in its OSGI exported packages. See
> the following exports:
> {noformat}
> karaf@root> headers 259
> Apache Derby 10.8 (259)
> -----------------------
> Manifest-Version = 1.0
> Ant-Version = Apache Ant 1.7.0
> Class-Path = derbyLocale_cs.jar derbyLocale_de_DE.jar derbyLocale_es.jar
> derbyLocale_fr.jar derbyLocale_hu.jar derbyLocale_it.jar derbyLocal
> e_ja_JP.jar derbyLocale_ko_KR.jar derbyLocale_pl.jar derbyLocale_pt_BR.jar
> derbyLocale_ru.jar derbyLocale_zh_CN.jar derbyLocale_zh_TW.jar
> Sealed = true
> Created-By = 2.4 (IBM Corporation)
> Bundle-Vendor = Apache Software Foundation
> Bundle-Activator = org.apache.derby.osgi.EmbeddedActivator
> Bundle-Name = Apache Derby 10.8
> Bundle-SymbolicName = derby
> Bundle-Version = 10.8.3000000.1405108
> Bundle-ManifestVersion = 2
> DynamicImport-Package =
> *
> Export-Package =
> org.apache.derby.authentication,
> org.apache.derby.database,
> org.apache.derby.io,
> org.apache.derby.jdbc,
> org.apache.derby.vti
> {noformat}
> {noformat}
> karaf@root> headers 250
> Apache Derby 10.9 (250)
> -----------------------
> Manifest-Version = 1.0
> Ant-Version = Apache Ant 1.7.1
> Class-Path = derbyLocale_cs.jar derbyLocale_de_DE.jar derbyLocale_es.jar
> derbyLocale_fr.jar derbyLocale_hu.jar derbyLocale_it.jar derbyLocal
> e_ja_JP.jar derbyLocale_ko_KR.jar derbyLocale_pl.jar derbyLocale_pt_BR.jar
> derbyLocale_ru.jar derbyLocale_zh_CN.jar derbyLocale_zh_TW.jar
> Sealed = true
> Created-By = 20.6-b01-415 (Apple Inc.)
> Bundle-Vendor = Apache Software Foundation
> Bundle-Activator = org.apache.derby.osgi.EmbeddedActivator
> Bundle-Name = Apache Derby 10.9
> Bundle-SymbolicName = derby
> Bundle-Version = 10.9.1000000.1344872
> Bundle-ManifestVersion = 2
> DynamicImport-Package =
> *
> Export-Package =
> org.apache.derby.authentication,
> org.apache.derby.database,
> org.apache.derby.io,
> org.apache.derby.jdbc,
> org.apache.derby.vti
> {noformat}
> This leads to problems, if other bundles imports derby packages with a
> specific version or version range (like spring-jdbc do):
> {noformat}
> karaf@root> headers 251
> Spring JDBC (251)
> -----------------
> Manifest-Version = 1.0
> ...
> Import-Package =
> ...
> org.apache.derby.impl.io;resolution:=optional;version="[10.5.0,
> 11.0.0)",
> org.apache.derby.jdbc;resolution:=optional;version="[10.5.0, 11.0.0)",
> ...
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
