You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Julian Reschke <re...@apache.org> on 2016/09/21 11:28:10 UTC
[VOTE] checking JDK compliance of old Jackrabbit branches / call to
EOL Jackrabbit 2.4
Hi there,
I just spent some time enabling the animal sniffer plugin in Jackrabbit
branches (see https://issues.apache.org/jira/browse/JCR-4025).
While trying to do so for 2.4, I noticed that although the pom.xml
claims that it is on JDK 5, there's code in there that relies on JDK 6
libraries, introduced over three years ago with
<https://fisheye6.atlassian.com/changelog/jackrabbit?cs=1516397>.
Proposal:
- change the pom.xml to required JDK 6 (and turn on JDK sniffing)
But also:
- officially end-of-life Jackrabbit 2.4 (for which the release of 2.4.6
would be the last one)
So let's vote:
[ ] declare end-of-life for Jackrabbit 2.4 after the upcoming 2.4.6
release
[ ] continue to maintain Jackrabbit 2.4
I'll wait 72 hours for feedback.
Best regards, Julian
Re: [VOTE] checking JDK compliance of old Jackrabbit branches / call
to EOL Jackrabbit 2.4
Posted by Davide Giannella <da...@apache.org>.
[X] declare end-of-life for Jackrabbit 2.4 after the upcoming 2.4.6
release
Davide
Re: [VOTE] checking JDK compliance of old Jackrabbit branches / call
to EOL Jackrabbit 2.4
Posted by Julian Reschke <ju...@gmx.de>.
On 2016-09-21 14:09, Julian Reschke wrote:
> On 2016-09-21 14:00, Marcel Reutegger wrote:
>> Hi,
>>
>> On 21/09/16 13:28, Julian Reschke wrote:
>>> Proposal:
>>>
>>> - change the pom.xml to required JDK 6 (and turn on JDK sniffing)
>>
>> Given there is just a minor change required, I would not lift
>> the minimal JDK version.
>
> -> <https://issues.apache.org/jira/browse/JCR-4026>
Fixed in <http://svn.apache.org/r1761722>.
>> [X] continue to maintain Jackrabbit 2.4
>>
>> Jackrabbit 2.4 is still in use in supported Products like CQ 5.5,
>> so I would rather like to maintain the branch for now.
>> ...
OK.
So my revised plan is:
a) Fix the issue (done, see above)
b) Continue the release process of 2.4.6 (this isn't important enough to
stop it)
c) Enable JDK sniffing for JDK 5 (see JCR-4025)
d) do a final release of 2.4 once it's really not needed anymore (and
then EOL it)
Best regards, Julian
Re: [VOTE] checking JDK compliance of old Jackrabbit branches / call
to EOL Jackrabbit 2.4
Posted by Julian Reschke <ju...@greenbytes.de>.
On 2016-09-21 14:00, Marcel Reutegger wrote:
> Hi,
>
> On 21/09/16 13:28, Julian Reschke wrote:
>> Proposal:
>>
>> - change the pom.xml to required JDK 6 (and turn on JDK sniffing)
>
> Given there is just a minor change required, I would not lift
> the minimal JDK version.
-> <https://issues.apache.org/jira/browse/JCR-4026>
> [X] continue to maintain Jackrabbit 2.4
>
> Jackrabbit 2.4 is still in use in supported Products like CQ 5.5,
> so I would rather like to maintain the branch for now.
>
> What happened to our EOL plan for 2.2 and 2.0? I know we discussed
> the plan, but can't remember if we ever officially announced it.
We (that is, Davide) announced deprecation of 2.2 on April, 25:
> The Apache Jackrabbit Team has decided that since the 2.2 branch of the
> project didn\u2019t receive any activity since 2012 and looks like not being
> used any more; to drop support and deprecate such version. Previous
> branch, tags and releases will still be available for future references.
>
> Regards
> Davide
Best regards, Julian
Re: [VOTE] checking JDK compliance of old Jackrabbit branches / call
to EOL Jackrabbit 2.4
Posted by Marcel Reutegger <mr...@adobe.com>.
Hi,
On 21/09/16 13:28, Julian Reschke wrote:
> Proposal:
>
> - change the pom.xml to required JDK 6 (and turn on JDK sniffing)
Given there is just a minor change required, I would not lift
the minimal JDK version.
[X] continue to maintain Jackrabbit 2.4
Jackrabbit 2.4 is still in use in supported Products like CQ 5.5,
so I would rather like to maintain the branch for now.
What happened to our EOL plan for 2.2 and 2.0? I know we discussed
the plan, but can't remember if we ever officially announced it.
Regards
Marcel