It's something we've not talked about I guess but I think it'd be good to commit to compatibility within minor versions; allowing breakage on majors... which would mean backing jetty down now, and explicitly say that the 0.3.x line will be >= Java 7...
--tim On Thu, Nov 6, 2014 at 2:50 PM, Andrew <[email protected]> wrote: > Java 6 was introduced in Dec 2006, Oracle declared it end of life in > February 2013. > Java 7 was introduced in July 2011. > Java 8 was introduced in March 2014. > > Based on this, I suggest that we remove compatibility with Java 6. > > However, if we want to maintain compatibility, I could look at downgrading > back to Jetty 8 (which would still be much better than the Jetty 6 that > comes with hadoop) > > On Wed, Nov 5, 2014 at 9:18 PM, Aaron McCurry <[email protected]> wrote: > >> So Andrew was nice enough to cleanup all of our pom files and update Jetty >> so that the console could make use of a newer version of Jetty for variety >> of reasons. However I believe that Jetty 9.x relies on Java 7, and this >> breaks our backwards compatibility with Java 6. >> >> Below is the error that Jenkins is reporting when building with Java 6. >> >> >> https://builds.apache.org/job/Blur-master-jdk6/org.apache.blur$blur-console/855/testReport/junit/org.apache.blur.console.util/NodeUtilTest/testGetControllerStatus/ >> >> I wanted to get some thoughts on this issue how we should handle it now and >> going forward how to deal with newer libraries. Basically when are we >> going to cutoff support for Java 6? >> >> Aaron >>
