Felix Meschberger schrieb: > Hi, > > Jukka Zitting schrieb: >> Hi, >> >> On Thu, Apr 30, 2009 at 6:59 PM, Ian Boston <i...@tfd.co.uk> wrote: >>> With JR trunk having branched 1.x off and now heading for 2.0. >>> >>> What plans, if any does Sling have for moving to 2.0 and 283 support? >> With my Jackrabbit release manager hat on I'd recommend that Sling >> wait until Jackrabbit 2.0 is officially out before upgrading to JCR >> 2.0. > > I was starting to think on another track: Is it really correct to have > the OSGi bindings for Jackrabbit in the Sling project ? > > Wouldn't it be more logical that Jackrabbit would provide the jackrabbit > binding bundles (jcr/jackrabbit-core and jcr/jackrabbit-client and > probably also jcr/base itself) ? > > In fact, many Jackrabbit libraries already come as bundles > (jackrabbit-api, jackrabbit-jcr-commons, jackrabbit-jcr-rmi), why not > the rest also ? > > I tend to think, that we might keep the bundles around here at Sling for > the Jackrabbit 1.x line because we extended Jackrabbit to allow for > pluggable extensions. But for Jackrabbit 2.0 it might be different. > I think that Sling should be able to run on JCR 1.0 for a long time; we shouldn't tie us to a new version; however, of course we might have some optional functionality requiring JCR 2.0.
Carsten -- Carsten Ziegeler cziege...@apache.org
