[ http://issues.apache.org/jira/browse/DERBY-1730?page=all ]
Rick Hillegas updated DERBY-1730:
---------------------------------
Urgency: Urgent (was: Normal)
> 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: 10.2.1.0
> Reporter: Knut Anders Hatlen
> Assigned To: Knut Anders Hatlen
> Fix For: 10.2.1.0
>
> 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
