It might make sense to rate each bundle/OSGi-ified library in some way, e.g. (similar to Thread ratings):
OSGi Unsafe - library bundle contains a number of antipatterns that are anti-modular, anti-dynamic and/or otherwise hard to get working in OSGi. OSGi Safe - library bundle works fine under OSGi but doesn't provide any special support. OSGi Hot - library bundle has extra support for OSGi, e.g. provides services, has an Activator etc. I think in all 3 cases the level of OSGi support should be documented but I think that if a library isn't 'OSGi Hot' it can still be useful in many cases so shouldn't necessarily be excluded from the repo. Even some libraries that are 'OSGi Unsafe' and need some trickery to get working under OSGi might provide so much value by themselves that it may be worth swallowing the anti-pattern that goes with it, that's a decision for the consumer to make, IMHO... Just my thoughts, David On 27 January 2012 17:47, Marcel Offermans <marcel.offerm...@luminis.nl> wrote: > On Jan 27, 2012, at 16:59 PM, Pete Carapetyan wrote: > > If it's a big manifest with quadzillion imports, it's not modular - > right????. It may be theoretically usable in an OSGi environment, but it's > existence may do more harm than good if coupled with the wrong bundle. > > > +1 > > If you're sharing more than just your APIs, you've probably already made > consessions to modularity. > > Greetings, Marcel > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
