1.6 is fine by me. Working actively with a customer using IBM's JDK 1.6, which is still supported by IBM, will make me vote -1 on a move to 1.7 currently.
/Anders On Sat, Sep 27, 2014 at 8:01 PM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote: > Hi Kristian, > > On 9/27/14 7:23 PM, Kristian Rosenvold wrote: > >> We moved core to 1.6 some time ago. >> > > As far as i know starting with Maven 3.2.1...was the first one... > > > > >> Time to move everything else as well ? >> > > We have at the moment a large number of plugins which have minimum Maven > 2.2.1 (JDK 1.5)...and few are currently at Maven 2.0.6 (that's only for a > limited amount of time) > > The next round should be to lift up to Maven 3.0.5 at minimum which > implies to left Maven 2 finally behind..... > > Making it visible to people by using 3.X versions for the plugins or > something similar... > > ...afterwards i see the next round to lift up to Maven 3.1.1... > and after that i see the next lift up to Maven 3.2.1 which implies Java > 1.6...and so on.... > > It's a longer way...which takes time... > > >> Kristian (Who's ready to say "1.7" but we stop by 1.6 first :) >> >> > If we go the above path it's of course longer but more consistence from > the user point of view...using Maven 3.0.5 which works with Java 1.5 ...and > the plugins as well...etc... > > Of course from the technical point of view it's not that good ;-(... > > So from my site i would vote with +0 ... > > Kind regards > Karl-Heinz Marbaise > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
