Keep in mind that maven 3.0-3.1.x are still java 1.5 and we haven't put a version policy in place.
Personally speaking I'm fine with plugins requiring java 1.6 and maven 3.2.1 as a minimum, but I'd rather see 3.3.x get some legs first and I suspect we'll have a few 3.2.x releases as we have EOL'd 2.x On Sunday, 23 February 2014, Benson Margulies <bimargul...@gmail.com> wrote: > I propose to make releases of our parent stack that are suitable for > components and plugins that are making the leap to Java 1.6 and Maven > 3 as their base requirements. > > What do people think is the right approach in terms of what stays on > trunk and what goes on a branch, and whether to do anything > distinctive to the version numbers? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org <javascript:;> > For additional commands, e-mail: dev-h...@maven.apache.org <javascript:;> > > -- Sent from my phone
