[ http://issues.apache.org/jira/browse/DERBY-228?page=all ]
Samuel Andrew McIntyre closed DERBY-228:
----------------------------------------
Resolution: Fixed
Fix Version: 10.1.0.0
Fix included in snapshot posted 4/28/2005
> need some OSGI related changes to MANIFEST.MF
> ---------------------------------------------
>
> Key: DERBY-228
> URL: http://issues.apache.org/jira/browse/DERBY-228
> Project: Derby
> Type: Bug
> Components: Build tools
> Versions: 10.0.2.1
> Reporter: Myrna van Lunteren
> Assignee: Samuel Andrew McIntyre
> Priority: Minor
> Fix For: 10.1.0.0, 10.0.2.2
>
> The MANIFEST.MF for derby.jar file has some support details for OSGI.
> However, there are some issues with it:
> - the Bundle-version number does not change with each build.
> This would not be a problem if we'd never publish an intermediate build,
> but as we do (snapshots), the Bundle-version number should change.
> Having the same bundle-version over different builds can cause trouble
> updating to the next (snapshot) and may cause confusion over what is
> exactly in the bundle.
> We could add the buildnumber into the Bundle-version number.
> - Import-Package does not need java.sql
> Derby does need java.sql to function, but as it's in the java namespace,
> it will be loaded (if present) into every bundle that needs it even if
> not specified in the import package entry.
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
