2009/9/29 Niclas Hedhman <[email protected]> > On Tue, Sep 29, 2009 at 3:01 PM, Stuart McCulloch <[email protected]> > wrote: > > > Bnd has no knowledge that your bundle is a library or an active bundle, > > Of course it does; It sees "Bundle-Activator:" which is "this is an > active bundle"... >
I meant that it can't tell whether you intentionally set Bundle-Activator or accidentally left it set for a library which doesn't contain said class. ie. it can follow the instructions, but cannot know the dev's intent. > > I've seen people intentionally share Bundle-Activators between bundles, > > and AFAIK this is allowed by the OSGi specs - so it would be wrong to > > disallow it by throwing an error. > > Hmmmm.... Yeah, probably allowed but barely a good practice other than > for "frameworks" that takes care of components and stuff for you. > > > I guess a warning might encourage best-practice of keeping activators > > private, so feel free to log an issue (note: this would actually require > a > > change to Bnd, so no guarantees of getting such a warning added) > > Ok, fair enough. Create an issue where? > Felix JIRA, as that's where I keep track of any bnd/bundleplugin issues > Cheers > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > > I live here; http://tinyurl.com/2qq9er > I work here; http://tinyurl.com/2ymelc > I relax here; http://tinyurl.com/2cgsug > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > -- Cheers, Stuart
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
