You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Julian Reschke <re...@apache.org> on 2020/04/06 09:07:22 UTC
[DISCUSS] Oak 1.10 is retired, what does this mean for Jackrabbit
2.18?
Hi there,
so we just retired Oak's 1.10 branch, which has been replaced by Oak
1.22. Oak 1.22 uses Jackrabbit 2.20; Oak 1.10 was using Jackrabbit 2.18.
No other Oak branch needs Jackrabbit 2.18.
AFAIR, the main differences between 2.18 and 2.20 are:
- removal of jackrabbit-api (now in Oak)
- refactoring of jackrabbit-standalone (new artifact
jackrabbit-standalone-components)
- Remove all usage of java.security.acl.Group for Java 14 (JCR-4467),
causing one incompatible change in jcr-rmi's exported packages
So the switch from 2.18 to 2.20 *might* cause the need to re-compile and
adjust POMs.
As we did not plan to retire 2.18 yet, my proposal is to update the
roadmap (<http://jackrabbit.apache.org/jcr/jackrabbit-roadmap.html>),
and to plan for one final release later this year, then retire the
branch after that release.
Feedback appreciated.
Best regards, Julian
Re: Plan to retire Jackrabbit 2.18 branch
Posted by Julian Reschke <ju...@gmx.de>.
Am 24.11.2020 um 09:06 schrieb Julian Reschke:
> Hi there,
>
> I plan to retire ("end of life") the 2.18 branch of Jackrabbit on
> December 1.
>
> Citing <https://issues.apache.org/jira/browse/JCR-4552>:
>
>> Users of 2.18 should switch to the latest stable release of 2.20 (note
>> that 2.20 doesn't have jackrabbit-api anymore, it has been replaced by
>> oak-jackrabbit-api; the current version applicable to Jackrabbit
>> 2.20.2 is 1.34.0)
>>
>> What it'll mean in actual actions:
>>
>> links will be removed from the download page
>> news will be posted on the homepage
>> [announce] will be sent to jr-user, jr-dev, oak-dev
>> branch and tags WILL stay there
>> issues labeled "candidate_jcr_2_18" will be re-labeled
>> "candidate_jcr_2_16"
>>
>> See also http://jackrabbit.apache.org/jcr/downloads.html
>
> Feedback appreciated,
Hearing no objections, I will proceed with this today...
Best regards, Julian
Plan to retire Jackrabbit 2.18 branch
Posted by Julian Reschke <re...@apache.org>.
Hi there,
I plan to retire ("end of life") the 2.18 branch of Jackrabbit on
December 1.
Citing <https://issues.apache.org/jira/browse/JCR-4552>:
> Users of 2.18 should switch to the latest stable release of 2.20 (note that 2.20 doesn't have jackrabbit-api anymore, it has been replaced by oak-jackrabbit-api; the current version applicable to Jackrabbit 2.20.2 is 1.34.0)
>
> What it'll mean in actual actions:
>
> links will be removed from the download page
> news will be posted on the homepage
> [announce] will be sent to jr-user, jr-dev, oak-dev
> branch and tags WILL stay there
> issues labeled "candidate_jcr_2_18" will be re-labeled "candidate_jcr_2_16"
>
> See also http://jackrabbit.apache.org/jcr/downloads.html
Feedback appreciated,
Julian
Re: [DISCUSS] Oak 1.10 is retired, what does this mean for Jackrabbit
2.18?
Posted by Julian Reschke <ju...@gmx.de>.
On 07.04.2020 15:27, Marcel Reutegger wrote:
> Hi,
>
> Sounds good to me. +1
>
> Regards
> Marcel
Seeing just one +1 and no objections, I have opened
<https://issues.apache.org/jira/browse/JCR-4552> to track this.
Best regards, Julian
Re: [DISCUSS] Oak 1.10 is retired, what does this mean for Jackrabbit
2.18?
Posted by Julian Reschke <ju...@gmx.de>.
On 07.04.2020 15:27, Marcel Reutegger wrote:
> Hi,
>
> Sounds good to me. +1
>
> Regards
> Marcel
Seeing just one +1 and no objections, I have opened
<https://issues.apache.org/jira/browse/JCR-4552> to track this.
Best regards, Julian
Re: [DISCUSS] Oak 1.10 is retired, what does this mean for Jackrabbit
2.18?
Posted by Marcel Reutegger <mr...@adobe.com>.
Hi,
Sounds good to me. +1
Regards
Marcel
On 06.04.20, 11:07, "Julian Reschke" <re...@apache.org> wrote:
Hi there,
so we just retired Oak's 1.10 branch, which has been replaced by Oak
1.22. Oak 1.22 uses Jackrabbit 2.20; Oak 1.10 was using Jackrabbit 2.18.
No other Oak branch needs Jackrabbit 2.18.
AFAIR, the main differences between 2.18 and 2.20 are:
- removal of jackrabbit-api (now in Oak)
- refactoring of jackrabbit-standalone (new artifact
jackrabbit-standalone-components)
- Remove all usage of java.security.acl.Group for Java 14 (JCR-4467),
causing one incompatible change in jcr-rmi's exported packages
So the switch from 2.18 to 2.20 *might* cause the need to re-compile and
adjust POMs.
As we did not plan to retire 2.18 yet, my proposal is to update the
roadmap (<http://jackrabbit.apache.org/jcr/jackrabbit-roadmap.html>),
and to plan for one final release later this year, then retire the
branch after that release.
Feedback appreciated.
Best regards, Julian
Re: [DISCUSS] Oak 1.10 is retired, what does this mean for Jackrabbit
2.18?
Posted by Marcel Reutegger <mr...@adobe.com.INVALID>.
Hi,
Sounds good to me. +1
Regards
Marcel
On 06.04.20, 11:07, "Julian Reschke" <re...@apache.org> wrote:
Hi there,
so we just retired Oak's 1.10 branch, which has been replaced by Oak
1.22. Oak 1.22 uses Jackrabbit 2.20; Oak 1.10 was using Jackrabbit 2.18.
No other Oak branch needs Jackrabbit 2.18.
AFAIR, the main differences between 2.18 and 2.20 are:
- removal of jackrabbit-api (now in Oak)
- refactoring of jackrabbit-standalone (new artifact
jackrabbit-standalone-components)
- Remove all usage of java.security.acl.Group for Java 14 (JCR-4467),
causing one incompatible change in jcr-rmi's exported packages
So the switch from 2.18 to 2.20 *might* cause the need to re-compile and
adjust POMs.
As we did not plan to retire 2.18 yet, my proposal is to update the
roadmap (<http://jackrabbit.apache.org/jcr/jackrabbit-roadmap.html>),
and to plan for one final release later this year, then retire the
branch after that release.
Feedback appreciated.
Best regards, Julian