I did some research. The OSGi dependencies can be replaced to the OSS ones:
osgi-core to org.apache.felix:osgi-core:1.4.0 that is already in Fedora
osge-enterprise to org.ops4j.pax.jdbc:pax-jdbc-spec:0.6.0. This one is not there, but other OPS4J packages are in there, so I presume this one can be added too. Please confirm.
The only change other than dependency needed is due to a little older spec used:
Index: pgjdbc/src/main/java/org/postgresql/osgi/PGBundleActivator.java IDEA additional info: Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP <+>UTF-8 =================================================================== --- pgjdbc/src/main/java/org/postgresql/osgi/PGBundleActivator.java (revision 0f979c3bbe1a36e6614e3d448ea43de7be27448b) +++ pgjdbc/src/main/java/org/postgresql/osgi/PGBundleActivator.java (revision ) @@ -22,7 +22,7 @@ * This class is an OSGi Bundle Activator and should only be used internally by the OSGi Framework */ public class PGBundleActivator implements BundleActivator { - private ServiceRegistration<?> _registration; + private ServiceRegistration _registration;
public void start(BundleContext context) throws Exception { Dictionary<String, Object> properties = new Hashtable<String, Object>();
>So it seems like one solution to osgi is just to copy the sources into the project. These are all interfaces, and a minimal number of files, I think around 4
What's the problem with packaging OSGi interfaces as usual rpms (or whatever is used for packaging)? As for me, "copy&pasting <<minimal number of files, I think around 4>>" does not solve legal issues if there are any. On top of that, exposing OSGi interfaces as part of pgjdbc.jar would probably void OSGi compliance. The jar would just not load due to invalid contents. Vladimir
