Hi Richard, thanks a lot for the pointer, that worked for me. I must say, this is really an excellent mailing list.
Thanks to everyone here for your replies... Cheers --Toni Richard S. Hall wrote: > > If you want to separate the Felix framework from the OSGi API classes, > then you will have to do this manually, but this should be fairly > straightforward with the trunk, since trunk no longer overrides any OSGi > classes. For older versions of Felix, we had a few OSGi classes for > which we needed to provide our own version...and in the future we may > also do this again for optimization purposes. > > For now, though, if you just modify the framework pom.xml file to not > export any OSGi packages, then you will get a JAR that doesn't contain > any. > > -> richard > > On 8/12/09 5:10, eppleton wrote: >> 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 >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/APi-and-Implementation-in-separate-JARs-tp24931883p24938355.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]
