+0 j6 is EOL so shouldn't really be used anymore and didnt use it since months but excepted multi catch feature j7 will not help us a lot I think - that's for dev side. For CI side I think it can make sense to get rid of the j6 constraint but I don't know if that's really a constraint for us.
Romain Manni-Bucau @rmannibucau | Blog | Github | LinkedIn | Tomitriber 2016-03-25 9:35 GMT+01:00 Gerhard Petracek <gerhard.petra...@gmail.com>: > i agree with thomas > > regards, > gerhard > > > > 2016-03-25 9:23 GMT+01:00 Thomas Andraschko <andraschko.tho...@gmail.com>: > >> basically +1 >> Most of our customers are using 1.7 since this year. >> >> I just wonder whats the benefit for us? >> I think there are no language features which would improve our code base. >> >> 2016-03-25 3:25 GMT+01:00 John D. Ament <johndam...@apache.org>: >> >> > Hey guys, >> > >> > I've brought this topic up before without much positive response. I >> figure >> > I'll bring it up again. >> > >> > I'd like to propose that DeltaSpike 1.6 be the last minor release to >> > support Java 1.6. I suspect that most users are already using Java 7 or >> > higher. None of our builds in CI (builds.apache.org) currently run on >> 1.6 >> > either, so while we can say from a syntax standpoint we're 1.6 compliant >> > I'm not sure we can say from a JDK Library standpoint we don't rely on >> > anything from Java 7. >> > >> > We're one of the few projects that probably still supports Java 6 as a >> > mainline development, so I was hoping we could just cut 1.6 as 1.6 >> > compliant, if we need to cut patch releases of 1.6 to apply patches, but >> > with DeltaSpike 1.7 and on, focus on Java 7 and up. >> > >> > John >> > >>
