Niclas Hedhman <[EMAIL PROTECTED]> writes: > On Friday 27 April 2007 19:29, Aggelos Mpimpoudis wrote: >> Most people that have the same problem bundlize their third party >> libraries as independent bundles!!! >> http://www.eclipsezone.com/eclipse/forums/t54726.html > > The issue is sometimes (maybe too often) a lot bigger than sticking the > proper > Manifest entries in place. There are classloading, caching and threading > issues, that often interferes with proper OSGi practices. > > On the surface, the 3rd party libraries provides a lot of functionality, but > expect many of them to be bad OSGi citizens.
Dealing with 3rd party libraries can be a real hurdle for OSGi adoption. Recently I've been playing around with Scala and OSGi and it's been going pretty well. It wasn't until I started adding some Java libraries to my runtime that things became "un-fun." http://cubiclemuses.com/cm/blog/2007/back_to_java.html We, the OSGi community, need to do a better job at encouraging OSS projects to include OSGi information in their jars. I know this won't solve all the possible bugs, but it's an important first step. -- J Aaron Farr jadetower.com [US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
