Re: [VOTE] checking JDK compliance of old Jackrabbit branches / call to EOL Jackrabbit 2.4

2016-09-22 Thread Davide Giannella
[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

2016-09-21 Thread Julian Reschke
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

Re: [VOTE] checking JDK compliance of old Jackrabbit branches / call to EOL Jackrabbit 2.4

2016-09-21 Thread Julian Reschke
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. ->

Re: [VOTE] checking JDK compliance of old Jackrabbit branches / call to EOL Jackrabbit 2.4

2016-09-21 Thread Marcel Reutegger
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

[VOTE] checking JDK compliance of old Jackrabbit branches / call to EOL Jackrabbit 2.4

2016-09-21 Thread Julian Reschke
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