Given that Oracle have stated they will be more aggressive in forcing people to upgrade, eg -target (and I think -source too) will not got all the way down to 1.2 any more from JDK8 IIRC, we will need to sort out a few things:
- is toolchains the way to go? - have we good test coverage with toolchains? Specifically building a JavaEE .ear for a JavaEE 5 container (ie using all/most of our plugins)? Better yet would be building a J2EE 1.4 .ear but I suspect we'd be fine with the JDK 5.0 rather than strict spec conformance. (A lot of "big business" use old containers and have Sarbains-Oxley heavyweight change control, so changing app server is a "very big thing") - have we a good store for toolchains and integration tests? (Invoker skipping tests if certain toolchains are missing, reporting what toolchains are required, merging in toolchains, providing mock toolchains... And have we any other users than the JDK?) - what is the experience of Surefire so far (being the first to completely ditch JRE < 1.5) On Tuesday, 16 July 2013, Mirko Friedenhagen wrote: > On Jul 16, 2013 2:08 AM, "Arnaud Héritier" <[email protected]<javascript:;>> > wrote: > > > > Hi, > > > > Java 6 EOL was in feb and Maven and its plugins are always compatible > > with Java 5 (And probably various plugins with Java 4). > > Couldn't it be interesting to see which JDKs our users are using to see > > how we can schedule the end of support of Java 5 (and more). Perhaps a > > removal of Java 5 support in 3.2 or 3.5 ... > > Perhaps with a survey like this : > > > > https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewform > > What do you think ? > > Useful ? Useless > > Very, very useful. > > Regards > Mirko > -- Sent from my phone
