db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bpendle...@apache.org
Subject svn commit: r830545 - /db/derby/code/trunk/build.xml
Date Wed, 28 Oct 2009 13:59:27 GMT
Author: bpendleton
Date: Wed Oct 28 13:59:27 2009
New Revision: 830545

URL: http://svn.apache.org/viewvc?rev=830545&view=rev
Log:
DERBY-4120: derbyclient.jar is not a complete OSGi bundle

OSGi bundles are JAR files with special information in their manifest to
enable the OSGi class loader to provide dynamic load/unload functionality.

This change adds some additional information to the manifest of
derbyclient.jar to support its use as an OSGi bundle. In particular,
it marks the org.apache.derby.jdbc package as exported, since that package
contains the ClientDriver and ClientDataSource classes which applications
are likely to use directly.


Modified:
    db/derby/code/trunk/build.xml

Modified: db/derby/code/trunk/build.xml
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/build.xml?rev=830545&r1=830544&r2=830545&view=diff
==============================================================================
--- db/derby/code/trunk/build.xml (original)
+++ db/derby/code/trunk/build.xml Wed Oct 28 13:59:27 2009
@@ -1550,6 +1550,14 @@
       <param name="manifest.file" value="${derby.jar.dir}/lists/smfclient.mf"/>
     </antcall>
 
+    <!-- add extra osgi bits to manifest -->
+
+    <manifest file="${derby.jar.dir}/lists/smfclient.mf"  mode="update">
+      <attribute name="Bundle-SymbolicName" value="derbyclient"/>
+      <attribute name="DynamicImport-Package" value="*"/>
+      <attribute name="Export-Package" value="org.apache.derby.jdbc"/> 
+    </manifest> 
+
     <!-- declare the client driver for autoloading by the JDBC 4 DriverManager -->
     <antcall target="declare-autoloadable-driver">
       <param name="driver.name" value="org.apache.derby.jdbc.ClientDriver"/>



Mime
View raw message