Given the effective timetable of any 3.x release, I think it should be jdk8; though clarifying this on the dev list one more time may be wise.
- We need a longer time before forcing java7 on applications using Hadoop; a split from client to server libs where client is @ 7 would address that, albeit at a more complex build.
- Based on my experience with the Java 7 move, before applying this patch, it is absolutely critical that jenkins is working on Java 8. without the tests being stable first, it's impossible to be sure that the move took place properly.
- of course, the Jenkins change here would essentially be "kill the trunk & java7 builds; rename the java 8 one"
I just got a patch for one problem in there yesterday (
HADOOP-11846), but now it looks like there's another, HADOOP-11864
YARN on Java 8 is broken simply because someone thought it was a good idea to use 12345 as the port for all test runs, so breaking on parallel runs. That needs to be fixed to hide false alarms. I'm not going to do the code for that myself, but I promise to +1 a patch which does the port-scanning adequately.