+1 There is no reason to have *NEW* development of Maven be hampered by obsolete technology. If anyone can't upgrade their Java runtime for whatever reason, they probably won't upgrade to a new Maven version as well. 3.0.4 works rather well and anyone should really be tying down their plugin versions as well.
I'd even suggest upping the minimum required version of Maven 4 to be Java 7. A build system really can benefit from try with resources, NIO2 etc. Having build times be chopped down half would benefit the whole world: less time waiting, and less energy used for building. Martijn On Wed, Feb 6, 2013 at 9:37 PM, Olivier Lamy <ol...@apache.org> wrote: > Hi, > As we are now in 2013, it's probably time to think about that (again). > > Reading [1], even 1.6 won't be anymore updated after feb 2013. > > Can we say we are safe to go to 1.6 as minimum required ? > > NOTE: That will probably need a vote. So depending on how the thread > move, I will start a vote (or not). > > Thanks > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > [1] http://www.oracle.com/technetwork/java/eol-135779.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Become a Wicket expert, learn from the best: http://wicketinaction.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
