You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Felix Meschberger <fm...@adobe.com> on 2012/05/19 11:50:14 UTC

Update parent POM to JCR 2.0

Hi all,

Until now we have JCR API 1.0 as a managed dependency in the parent POM. If a bundle requires JCR 2.0 API that version is explicitly noted in the bundle's POM.

Now, JCR 2.0 has been out for quite a while and I doubt there are still current implementations of JCR 1.0 out there.

So, I think, that we might want to update the managed dependency to 2.0 as an exception to our rule stating to only refer to the lowest version providing the required API.

WDYT ?

Regards
Felix

Re: Update parent POM to JCR 2.0

Posted by Carsten Ziegeler <cz...@apache.org>.
+1

Carsten

2012/5/19 Justin Edelson <ju...@gmail.com>:
> +1
>
> On May 19, 2012, at 5:50 AM, Felix Meschberger <fm...@adobe.com> wrote:
>
>> Hi all,
>>
>> Until now we have JCR API 1.0 as a managed dependency in the parent POM. If a bundle requires JCR 2.0 API that version is explicitly noted in the bundle's POM.
>>
>> Now, JCR 2.0 has been out for quite a while and I doubt there are still current implementations of JCR 1.0 out there.
>>
>> So, I think, that we might want to update the managed dependency to 2.0 as an exception to our rule stating to only refer to the lowest version providing the required API.
>>
>> WDYT ?
>>
>> Regards
>> Felix



-- 
Carsten Ziegeler
cziegeler@apache.org

Re: Update parent POM to JCR 2.0

Posted by Justin Edelson <ju...@gmail.com>.
+1

On May 19, 2012, at 5:50 AM, Felix Meschberger <fm...@adobe.com> wrote:

> Hi all,
> 
> Until now we have JCR API 1.0 as a managed dependency in the parent POM. If a bundle requires JCR 2.0 API that version is explicitly noted in the bundle's POM.
> 
> Now, JCR 2.0 has been out for quite a while and I doubt there are still current implementations of JCR 1.0 out there.
> 
> So, I think, that we might want to update the managed dependency to 2.0 as an exception to our rule stating to only refer to the lowest version providing the required API.
> 
> WDYT ?
> 
> Regards
> Felix

Re: Update parent POM to JCR 2.0

Posted by Dascalita Dragos <dd...@gmail.com>.
+1
I was waiting for this !

Dragos


On Sat, May 19, 2012 at 12:50 PM, Felix Meschberger <fm...@adobe.com>wrote:

> Hi all,
>
> Until now we have JCR API 1.0 as a managed dependency in the parent POM.
> If a bundle requires JCR 2.0 API that version is explicitly noted in the
> bundle's POM.
>
> Now, JCR 2.0 has been out for quite a while and I doubt there are still
> current implementations of JCR 1.0 out there.
>
> So, I think, that we might want to update the managed dependency to 2.0 as
> an exception to our rule stating to only refer to the lowest version
> providing the required API.
>
> WDYT ?
>
> Regards
> Felix