OK, so here is our policy:

The development line of Maven core should require a minimum JRE version
> that is no older than 18 months after the end of Oracle's public updates
> for that JRE version at the time that the first version of the development
> line was released, but may require a higher minimum JRE version if other
> requirements dictate a higher JRE version


(Source:
https://cwiki.apache.org/confluence/display/MAVEN/Version+number+policy)

OK, so it's a draft policy... but we've all been silent on the draft, so
lazy consensus!

Now in http://www.oracle.com/technetwork/java/javase/eol-135779.html they
state:

after April 2015, Oracle will not post further updates of Java SE 7 to its
> public download sites


So per our (draft) version number policy, we can keep Java 7 as the
baseline :-( or we can choose to upgrade code to Java 8 (because we want to
use lambdas... there's a requirement)

Dang! And I was hoping for a hard and fast "let's just drop Java 7" line...
oh well... we might have to argue this one out

On 29 November 2015 at 23:14, Stephen Connolly <
[email protected]> wrote:

> w00t new minor and we get to drop Java 7
>
>
> On Sunday 29 November 2015, Tibor Digana <[email protected]>
> wrote:
>
>> +1: go for it
>>
>> On Sun, Nov 29, 2015 at 4:27 PM, Hervé BOUTEMY <[email protected]>
>> wrote:
>>
>> > Now that Maven 3.3.9 is out and seems pretty stable, any objection to
>> > switch
>> > to 3.4.0-SNAPSHOT?
>> >
>> > I want to merge MNG-5878 new feature...
>> >
>> > Regards,
>> >
>> > Hervé
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [email protected]
>> > For additional commands, e-mail: [email protected]
>> >
>> >
>>
>>
>> --
>> Cheers
>> Tibor
>>
>
>
> --
> Sent from my phone
>

Reply via email to