I would have expected our first step would be to set source and target to 1.6, and move the Maven core dependencies to 3.0.x. I don't see why the fact that the core was compiled with target=1.5 would have any impact here.
I'd like to avoid a disorganized process of individual plugins and components getting complex stuff into their poms, each one a bit different. On Sun, Feb 23, 2014 at 1:43 PM, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
