[ https://issues.apache.org/jira/browse/DERBY-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-1945.
------------------------------------
Resolution: Duplicate
Fix Version/s: 10.6.0.0
10.5.4.0
10.4.3.0
10.3.3.1
It seems like the primary issue here was the Bundle-SymbolicName, and that
was taken care of in DERBY-3730, so I'm resolving this as a duplicate of
DERBY-3730.
> Need changes to manifest for OSGi environment
> ---------------------------------------------
>
> Key: DERBY-1945
> URL: https://issues.apache.org/jira/browse/DERBY-1945
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.1.3.1
> Reporter: Stephen Felts
> Assignee: Bryan Pendleton
> Priority: Minor
> Fix For: 10.3.3.1, 10.4.3.0, 10.5.4.0, 10.6.0.0
>
>
> When running with Derby in an OSGi environment, there are a couple of changes that are
needed in the manifest.
> 1. The manifest does not have a Bundle Symbolic Name. This causes some tools not to
recognize it as an OSGi bundle and some things don't work nicely without the symbolic name.
> Add Bundle-SymbolicName: derby to the manifest.
> 2. I'm working with a product that creates dynamic proxies for all of the interfaces
like Connection, Statement, etc.
> As part of doing that, it needs access to all classes that are referenced in those interface
classes.
> There are several classes that are referenced in packages that are not exported. The
following exports needed to be added to the manifest:
> org.apache.derby.iapi.jdbc
> org.apache.derby.impl.jdbc
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|