On 30.08.2011 15:36, Richard S. Hall wrote: > While I agree with you in spirit, generic caps/reqs won't really help > when it comes to preventing one bundle from starting before another, > since they address resolve-time dependencies, not activation-time > dependencies. The weaver must be active before it can weave any classes.
True, true..I was alluding to an IMHO Inevitable Future where reqs/caps are used by whatever sugarcoating deployment doodad on top of the generic framework (which should not be concerned with this). I guess once people start to manipulate the lower levels directly, they are responsible for putting them together in the right order and get to keep any leftovers.. cheers, -h --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
