db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1730) Manifest file doesn't contain OSGi attributes
Date Sat, 19 Aug 2006 18:53:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1730?page=all ]

Andrew McIntyre updated DERBY-1730:

    Fix Version/s:
       Derby Info:   (was: [Patch Available])

Applied patch, verified it fixes this issue. Committed to trunk with revision 432859. Marking
Fix In and leaving open to make sure this gets merged to

> Manifest file doesn't contain OSGi attributes
> ---------------------------------------------
>                 Key: DERBY-1730
>                 URL: http://issues.apache.org/jira/browse/DERBY-1730
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>             Fix For:
>         Attachments: manifest.diff
> I see this after the check-in of DERBY-1362. With osgi.jar in tools/java, 'ant buildjars'
does not add the OSGi attributes to derby.jar's manifest. Instead, a file named ${manifest.file}
is created in the root of the source tree. This file contains what should have been in the
manifest, for instance:
> Manifest-Version: 1.0
> Ant-Version: Apache Ant 1.6.5
> Created-By: diablo-1.5.0_07-b00 (Sun Microsystems Inc.)
> Bundle-Activator: org.apache.derby.osgi.EmbeddedActivator
> DynamicImport-Package: *
> Export-Package: org.apache.derby.authentication,org.apache.derby.datab
>  ase,org.apache.derby.io,org.apache.derby.jdbc,org.apache.derby.vti
> This seems to be caused by build.xml containing a reference to "${manifest.file}" at
a location where manifest.file is not bound to a value. The attached patch (manifest.diff)
fixes the issue by replacing "${manifest.file}" with "${derby.jar.dir}/lists/smf.mf".

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


View raw message