On 11 Feb 2010, at 08:32, Felix Meschberger wrote: > Hi, > > At first I am as concerned as you are. > > Yet, I could justify such a move as follows: > > * jcr.api provides a new Service Interface > * jcr.api does not export the official JCR API any longer > * we need a JCR API in Sling > > So, while I really think we should keep the default JCR API dependency > to 1.0 in Sling, it looks ok to deploy the JCR 2.0 API in Sling. > > Another solution would be to provide a transitional JCR 1.0 API wrapper > bundle in Sling. > > WDYT ?
That sounds fine, no need for a wrapper, just so we know that until the jump to 2.0 is made in the server bundle everything will continue to work with the 1.0 compliant server bundle. Thanks Ian > > Regards > Felix > > On 11.02.2010 09:25, Ian Boston wrote: >> Justin, all, >> >> If there is going to be a transition to Jackrabbit 2, can we please make >> certain that there is a known commit in a stable state which people can bind >> to if they are working to milestone deadlines. >> >> I haven't worked through the details of including the JCR 2.0 API yet, but I >> am nervous having it there with a JCR 1.0 implementation might cause >> problems. Is it going to cause problems ? >> >> Ian >> >> On 11 Feb 2010, at 02:13, [email protected] wrote: >> >>> +++ sling/trunk/launchpad/builder/src/main/bundles/list.xml Thu Feb 11 >>> 02:13:07 2010 >>> @@ -237,7 +237,12 @@ >>> <bundle> >>> <groupId>org.apache.sling</groupId> >>> <artifactId>org.apache.sling.jcr.api</artifactId> >>> - <version>2.0.2-incubator</version> >>> + <version>2.0.7-SNAPSHOT</version> >>> + </bundle> >>> + <bundle> >>> + <groupId>javax.jcr</groupId> >>> + <artifactId>jcr</artifactId> >>> + <version>2.0</version> >>> </bundle> >>> <bundle> >>> <groupId>org.apache.sling</groupId> >> >>
