On Mar 30, 2010, at 5:02 PM, Ian Boston <[email protected]> wrote: > > On 30 Mar 2010, at 07:15, Felix Meschberger wrote: > >> So, how about moving the node type definition to the jcr.resource >> bundle ? > > +1, > Its the only cnd file outside jcr.resource in the core code. > and sling:target is referenced in jcr.resource anyway. > If this is the case, then the cnd files should absolutely be in the jcr.resource bundle.
> btw, I'd also like to avoid Require-Bundle if possible, partly > because it may prevent replacement bundles providing the same > functionality, if there was a "Require-Capability" in OSGi it might > be more appropriate. > I understand the arguments against Require-Bundle, but I'm not aware of a way to describe a dependency between bundle resources which the bundle resolver will take into account (i.e. Something like Require/ Provide-Capability). The only other option which comes to mind is to export and import fake packages, but that seems like it would cause problems at some point. So while moving the CND around is a good solution for this particular issue, I personally am still looking for a good way to describe dependencies between bundle resources, most significantly nodetypes, initial content, and bundle-provided resources. In all of these cases, I'm less concerned with start order as I am with presence. Justin > Ian
