You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Ian Boston <ie...@tfd.co.uk> on 2010/02/11 09:25:18 UTC
Re: svn commit: r908798 - in /sling/trunk: bundles/jcr/api/ bundles/jcr/api/src/main/java/org/apache/sling/jcr/api/ bundles/jcr/base/src/main/java/org/apache/sling/jcr/base/ bundles/jcr/base/src/main/java/org/apache/sling/jcr/base/internal/ bundles/jcr/bas...
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, justin@apache.org 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>
Re: svn commit: r908798 - in /sling/trunk: bundles/jcr/api/ bundles/jcr/api/src/main/java/org/apache/sling/jcr/api/
bundles/jcr/base/src/main/java/org/apache/sling/jcr/base/ bundles/jcr/base/src/main/java/org/apache/sling/jcr/base/internal/
bundles/jcr/bas...
Posted by Justin Edelson <ju...@gmail.com>.
Felix basically captured why I did this - jcr.api has a new interface
(NamespaceMapper) which jcr.base now depends upon. And obviously, all
the bundles which import javax.jcr allow for version 2.0 to be used.
That said, I would really like to see trunk upgraded to JCR 2/Jackrabbit
2 throughout. I don't mind maintaining a branch for this purpose, but
would obviously prefer not to.
Justin
On 2/11/10 3:38 AM, Ian Boston wrote:
>
> 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, justin@apache.org 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>
>>>
>>>
>
Re: svn commit: r908798 - in /sling/trunk: bundles/jcr/api/ bundles/jcr/api/src/main/java/org/apache/sling/jcr/api/ bundles/jcr/base/src/main/java/org/apache/sling/jcr/base/ bundles/jcr/base/src/main/java/org/apache/sling/jcr/base/internal/ bundles/jcr/bas...
Posted by Ian Boston <ie...@tfd.co.uk>.
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, justin@apache.org 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>
>>
>>
Re: svn commit: r908798 - in /sling/trunk: bundles/jcr/api/ bundles/jcr/api/src/main/java/org/apache/sling/jcr/api/
bundles/jcr/base/src/main/java/org/apache/sling/jcr/base/ bundles/jcr/base/src/main/java/org/apache/sling/jcr/base/internal/
bundles/jcr/bas...
Posted by Felix Meschberger <fm...@gmail.com>.
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 ?
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, justin@apache.org 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>
>
>