Thanks for the lightning-fast reply! I've already got the OSGi API for 4.1 from Maven Central:
But there are several problems with that: 1. as you said it's not 4.2 2. I still need a felix.jar without the API classes: What I want is this (For background: NB module system is quite similar to OSGi): I've got 5 modules (= almost the same as bundles): "FrameWork Support UI", "OSGi API 4.2", "Felix Support", "Knopflerfish Support", "ServiceProviderInterface" "FrameWork Support" bundle depends on "OSGi API 4.2" & "ServiceProviderInterface". At runtime it looks for registered Service Providers that provide e.g. a BundleContext. "Felix Support" and "Knopflerfish Support" depend on "OSGi API 4.2" & "ServiceProviderInterface" as well. Both implement the Service Provider Interface. Now the Problem is, if felix.jar or knopflerfish.jar (or whatever it's called) contains BundleContext, I won't be able to cast Felix BundleContext to the API BundleContext, but I want to keep this loosely coupled design. That's why I need a felix.jar without the APi classes. --Toni Stuart McCulloch wrote: > > 2009/8/12 Houtman, Roland <[email protected]> > >> Hi, >> >> You can download the osgi- core and compendium interface jars from >> http://www.osgi.org/Release4/Download >> >> You can either subscribe or click "No thanks, I'd like to go straight >> to the download." >> > > FYI as Alin mentioned in another thread, the official OSGi API jars are > now > on Maven central: > > http://repo2.maven.org/maven2/org/osgi/org.osgi.core/4.1.0/ > http://repo2.maven.org/maven2/org/osgi/org.osgi.compendium/4.1.0/ > > so you can compile against these, independent of the actual framework > you're > going to use > > note that these jars don't have the changes in the 4.2 API (such as the > new > launching API) > but once it's released (later this year?) the 4.2 API jars will also be > available on central > > Also E.g. >> The bundleRepository (OBR) has 2 separate jars which you can download >> from Felix downloads >> Called "OSGi OBR service API" then there is the implementation "Bundle >> repository" >> >> Regards, >> Roland >> >> -----Original Message----- >> From: eppleton [mailto:[email protected]] >> Sent: woensdag 12 augustus 2009 11:10 >> To: [email protected] >> Subject: APi and Implementation in separate JARs >> >> >> Hi, >> >> Is there a way to get the classes of the OSGi API and the Felix >> implementation in two separate JARs? >> >> I'm creating a plugin for NetBeans to register and administrate OSGi >> containers. Felix ist the default, but I want my tool to rely on the API >> only in order to be able to plugin other implementations (e.g. >> Knopflerfish). So the UI can display information for a Bundle regardless >> where it comes from. >> >> If there's nothing like that out-of-the-box, I'll do it manually. The >> question then is: Would that work since it seems I'll also have to split >> up the manifest then... >> >> Thanks >> >> --Toni >> >> >> -- >> View this message in context: >> http://www.nabble.com/APi-and-Implementation-in-separate-JARs-tp24931883 >> p24931883.html<http://www.nabble.com/APi-and-Implementation-in-separate-JARs-tp24931883%0Ap24931883.html> >> Sent from the Apache Felix - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > -- > Cheers, Stuart > > -- View this message in context: http://www.nabble.com/APi-and-Implementation-in-separate-JARs-tp24931883p24933898.html Sent from the Apache Felix - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
