Hi, I'll just comment on those were I have a different opinion or additional comment :)
Felix Meschberger wrote: > bundles/jcr/base > Provides an abstract base implementation of the SlingRepository > interface and has Jackrabbit dependencies. > --> Investigate separation of Jackrabbit specific and generic > JCR parts and split the bundle in two: The Jackrabbit part goes > to Jackrabbit, the JCR-only part remains here Not sure if it is worth to separate, I would just donate everything to Jackrabbit. If other repository implementations are interested we can investigate further. > bundles/jcr/contentloader > Initial Content Loader, currently has dependency on Jackrabbit > API for ACL stuff. For JCR 2.0 this will be converted into a > pure JCR 2.0 dependency, hence be completely independent of > Jackrabbit > --> Keep it or offer to Jackrabbit ? Keep it. > bundles/jcr/ocm > OSGi bundle with Jackrabbit-OCM providing a Sling > AdapterFactory for resources. Plugs heavily into Sling. > --> Keep it here or offer to Jackrabbit ? Keep it > > contrib/jcr/jackrabbit-api > Old OSGi bundle wrapping of Jackrabbit API. This is not used > any longer, since Jackrabbit already provides OSGi bundles of > some libraries, including the Jackrabbit API > --> Deprecate and remove sometime in the future (move to "attic"?) I think we can just remove it. Carsten -- Carsten Ziegeler [email protected]
