You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Julian Reschke <re...@apache.org> on 2016/10/26 13:13:29 UTC
[ANNOUNCE] Plan for disruptive changes to Jackrabbit WebDAV library
Hi there,
context: <https://issues.apache.org/jira/browse/JCR-2406>
Summary: we want to get rid of our dependency of httpclient 3.*
(<http://hc.apache.org/httpclient-3.x/>), which as been end-of-lifed
quite some time ago.
This will affect our public API, which extends classes from it.
The current plan is to add a new set of APIs (probably based on
HttpClient 4.5.x) in the next stable Jackrabbit release 2.14, planned to
be released in Spring 2017. At that point, we'll also deprecate the old
classes.
Later on, we would *remove* the httpclient 3.x dependency and the old
classes -- the plan would be to do that in the subsequent stable
release: Jackrabbit 2.16, which could come out in Spring 2018.
At that point, users of the old API can:
- either continue using Jackrabbit 2.14.*, or
- update their own code to work with Jackrabbit 2.16.*.
Feedback appreciated -- either here, or in
<https://issues.apache.org/jira/browse/JCR-2406>.
Best regards, Julian
Re: [ANNOUNCE] Plan for disruptive changes to Jackrabbit WebDAV
library
Posted by Julian Reschke <ju...@gmx.de>.
On 2016-10-26 15:13, Julian Reschke wrote:
> Hi there,
>
> context: <https://issues.apache.org/jira/browse/JCR-2406>
>
> Summary: we want to get rid of our dependency of httpclient 3.*
> (<http://hc.apache.org/httpclient-3.x/>), which as been end-of-lifed
> quite some time ago.
>
> This will affect our public API, which extends classes from it.
>
> The current plan is to add a new set of APIs (probably based on
> HttpClient 4.5.x) in the next stable Jackrabbit release 2.14, planned to
> be released in Spring 2017. At that point, we'll also deprecate the old
> classes.
>
> Later on, we would *remove* the httpclient 3.x dependency and the old
> classes -- the plan would be to do that in the subsequent stable
> release: Jackrabbit 2.16, which could come out in Spring 2018.
>
> At that point, users of the old API can:
>
> - either continue using Jackrabbit 2.14.*, or
>
> - update their own code to work with Jackrabbit 2.16.*.
>
> Feedback appreciated -- either here, or in
> <https://issues.apache.org/jira/browse/JCR-2406>.
>
> Best regards, Julian
Hi there, here's an update:
1) I have added individual tasks to
<https://issues.apache.org/jira/browse/JCR-2406>. Most of them are
supposed to happen before we cut 2.14. The actual removal of the
HttpClient3 code would happen when we release 2.15.0.
2) For those interested, the actual work is happening in
<https://github.com/reschke/jackrabbit/tree/JCR-2406>.
Best regards, Julian
Re: [ANNOUNCE] Plan for disruptive changes to Jackrabbit WebDAV
library
Posted by Julian Reschke <ju...@gmx.de>.
On 2016-10-26 15:13, Julian Reschke wrote:
> Hi there,
>
> context: <https://issues.apache.org/jira/browse/JCR-2406>
>
> Summary: we want to get rid of our dependency of httpclient 3.*
> (<http://hc.apache.org/httpclient-3.x/>), which as been end-of-lifed
> quite some time ago.
>
> This will affect our public API, which extends classes from it.
>
> The current plan is to add a new set of APIs (probably based on
> HttpClient 4.5.x) in the next stable Jackrabbit release 2.14, planned to
> be released in Spring 2017. At that point, we'll also deprecate the old
> classes.
>
> Later on, we would *remove* the httpclient 3.x dependency and the old
> classes -- the plan would be to do that in the subsequent stable
> release: Jackrabbit 2.16, which could come out in Spring 2018.
>
> At that point, users of the old API can:
>
> - either continue using Jackrabbit 2.14.*, or
>
> - update their own code to work with Jackrabbit 2.16.*.
>
> Feedback appreciated -- either here, or in
> <https://issues.apache.org/jira/browse/JCR-2406>.
>
> Best regards, Julian
Hi there, here's an update:
1) I have added individual tasks to
<https://issues.apache.org/jira/browse/JCR-2406>. Most of them are
supposed to happen before we cut 2.14. The actual removal of the
HttpClient3 code would happen when we release 2.15.0.
2) For those interested, the actual work is happening in
<https://github.com/reschke/jackrabbit/tree/JCR-2406>.
Best regards, Julian
Re: [ANNOUNCE] Plan for disruptive changes to Jackrabbit WebDAV
library
Posted by Julian Reschke <ju...@gmx.de>.
On 2016-10-27 08:27, Tobias Bocanegra wrote:
> Great.
> Let me know if you need help :-)
>
> On a related topic, what is the test coverage of jackrabbit webdav?
> IIRC, we used to run litmus against it. Is this still a valid test?
>
> Regards, Toby
It's tested implicitly when using spi2dav or jcr2dav...
Best regards, Julian
Re: [ANNOUNCE] Plan for disruptive changes to Jackrabbit WebDAV library
Posted by Tobias Bocanegra <tr...@apache.org>.
Great.
Let me know if you need help :-)
On a related topic, what is the test coverage of jackrabbit webdav? IIRC,
we used to run litmus against it. Is this still a valid test?
Regards, Toby
On Thu, Oct 27, 2016 at 3:22 PM, Julian Reschke <ju...@gmx.de>
wrote:
> On 2016-10-27 02:25, Tobias Bocanegra wrote:
>
>> Hi,
>>
>> I also think we should expedite this, so we have a 3.x free version by
>> the end of this year. btw, are there any 3.x usages in Oak?
>>
>> WDYT?
>>
>> regards, toby
>>
>
> a) Let's get started and then figure out whether we can accelerate this.
>
> b) AFAIK: no.
>
> Best regards, Julian
>
Re: [ANNOUNCE] Plan for disruptive changes to Jackrabbit WebDAV
library
Posted by Julian Reschke <ju...@gmx.de>.
On 2016-10-27 02:25, Tobias Bocanegra wrote:
> Hi,
>
> I also think we should expedite this, so we have a 3.x free version by
> the end of this year. btw, are there any 3.x usages in Oak?
>
> WDYT?
>
> regards, toby
a) Let's get started and then figure out whether we can accelerate this.
b) AFAIK: no.
Best regards, Julian
Re: [ANNOUNCE] Plan for disruptive changes to Jackrabbit WebDAV library
Posted by Tobias Bocanegra <tr...@apache.org>.
Hi,
I also think we should expedite this, so we have a 3.x free version by the
end of this year. btw, are there any 3.x usages in Oak?
WDYT?
regards, toby
On Thu, Oct 27, 2016 at 3:08 AM, Julian Reschke <ju...@gmx.de>
wrote:
> On 2016-10-26 17:28, Roy T. Fielding wrote:
>
>> On Oct 26, 2016, at 6:13 AM, Julian Reschke <re...@apache.org> wrote:
>>>
>>> Hi there,
>>>
>>> context: <https://issues.apache.org/jira/browse/JCR-2406>
>>>
>>> Summary: we want to get rid of our dependency of httpclient 3.* (<
>>> http://hc.apache.org/httpclient-3.x/>), which as been end-of-lifed
>>> quite some time ago.
>>>
>>> This will affect our public API, which extends classes from it.
>>>
>>> The current plan is to add a new set of APIs (probably based on
>>> HttpClient 4.5.x) in the next stable Jackrabbit release 2.14, planned to be
>>> released in Spring 2017. At that point, we'll also deprecate the old
>>> classes.
>>>
>>> Later on, we would *remove* the httpclient 3.x dependency and the old
>>> classes -- the plan would be to do that in the subsequent stable release:
>>> Jackrabbit 2.16, which could come out in Spring 2018.
>>>
>>> At that point, users of the old API can:
>>>
>>> - either continue using Jackrabbit 2.14.*, or
>>>
>>> - update their own code to work with Jackrabbit 2.16.*.
>>>
>>> Feedback appreciated -- either here, or in <
>>> https://issues.apache.org/jira/browse/JCR-2406>.
>>>
>>> Best regards, Julian
>>>
>>
>> That seems like an awful long time. Assuming no one objects to the need
>> to update,
>> I suggest that the timeline should take care of itself. IOW, if someone
>> commits an
>> updated API then it can be released "in the next release", after which
>> the old API
>> can be removed and 2.16.0 considered for the next release.
>>
>> That can all be done next week, if anyone gets excited. ;-)
>>
>> ....Roy
>>
>
> I'm all for speed.
>
> Just to be clear: 2.16 is the "next" release after 2.14 (we use odd
> numbers for the cuts from trunk as unstable releases).
>
> Best regards, Julian
>
>
Re: [ANNOUNCE] Plan for disruptive changes to Jackrabbit WebDAV
library
Posted by Julian Reschke <ju...@gmx.de>.
On 2016-10-26 17:28, Roy T. Fielding wrote:
>> On Oct 26, 2016, at 6:13 AM, Julian Reschke <re...@apache.org> wrote:
>>
>> Hi there,
>>
>> context: <https://issues.apache.org/jira/browse/JCR-2406>
>>
>> Summary: we want to get rid of our dependency of httpclient 3.* (<http://hc.apache.org/httpclient-3.x/>), which as been end-of-lifed quite some time ago.
>>
>> This will affect our public API, which extends classes from it.
>>
>> The current plan is to add a new set of APIs (probably based on HttpClient 4.5.x) in the next stable Jackrabbit release 2.14, planned to be released in Spring 2017. At that point, we'll also deprecate the old classes.
>>
>> Later on, we would *remove* the httpclient 3.x dependency and the old classes -- the plan would be to do that in the subsequent stable release: Jackrabbit 2.16, which could come out in Spring 2018.
>>
>> At that point, users of the old API can:
>>
>> - either continue using Jackrabbit 2.14.*, or
>>
>> - update their own code to work with Jackrabbit 2.16.*.
>>
>> Feedback appreciated -- either here, or in <https://issues.apache.org/jira/browse/JCR-2406>.
>>
>> Best regards, Julian
>
> That seems like an awful long time. Assuming no one objects to the need to update,
> I suggest that the timeline should take care of itself. IOW, if someone commits an
> updated API then it can be released "in the next release", after which the old API
> can be removed and 2.16.0 considered for the next release.
>
> That can all be done next week, if anyone gets excited. ;-)
>
> ....Roy
I'm all for speed.
Just to be clear: 2.16 is the "next" release after 2.14 (we use odd
numbers for the cuts from trunk as unstable releases).
Best regards, Julian
Re: [ANNOUNCE] Plan for disruptive changes to Jackrabbit WebDAV library
Posted by "Roy T. Fielding" <fi...@gbiv.com>.
> On Oct 26, 2016, at 6:13 AM, Julian Reschke <re...@apache.org> wrote:
>
> Hi there,
>
> context: <https://issues.apache.org/jira/browse/JCR-2406>
>
> Summary: we want to get rid of our dependency of httpclient 3.* (<http://hc.apache.org/httpclient-3.x/>), which as been end-of-lifed quite some time ago.
>
> This will affect our public API, which extends classes from it.
>
> The current plan is to add a new set of APIs (probably based on HttpClient 4.5.x) in the next stable Jackrabbit release 2.14, planned to be released in Spring 2017. At that point, we'll also deprecate the old classes.
>
> Later on, we would *remove* the httpclient 3.x dependency and the old classes -- the plan would be to do that in the subsequent stable release: Jackrabbit 2.16, which could come out in Spring 2018.
>
> At that point, users of the old API can:
>
> - either continue using Jackrabbit 2.14.*, or
>
> - update their own code to work with Jackrabbit 2.16.*.
>
> Feedback appreciated -- either here, or in <https://issues.apache.org/jira/browse/JCR-2406>.
>
> Best regards, Julian
That seems like an awful long time. Assuming no one objects to the need to update,
I suggest that the timeline should take care of itself. IOW, if someone commits an
updated API then it can be released "in the next release", after which the old API
can be removed and 2.16.0 considered for the next release.
That can all be done next week, if anyone gets excited. ;-)
....Roy