There’s a bunch of stuff that needs to happen at the Jenkins level: * Kill off the JDK7 trunk builds for HADOOP, HDFS, MAPRED, YARN * Remove JDK7 from pre-commit for HADOOP, HDFS, MAPRED, YARN
One thing that needs to happen in the Apache Yetus project: * Wait until YETUS-369 has been written and committed to re-enable JDK7 for pre-commit (This effectively means that *ALL* JDK7 testing will *ONLY* be happening in the regularly scheduled builds) One thing that really should happen in the Apache Hadoop project: * Remove JDK7 from trunk Dockerfile I’ll start banging on this stuff over the next few days. > On May 16, 2016, at 3:58 PM, Andrew Wang <[email protected]> wrote: > > Very happy to announce that we've committed HADOOP-11858. I'm looking > forward to writing my first lambda in Java. I also attached a video to the > JIRA so we can all relive this moment in Hadoop development history. > > It sounds like there's some precommit work to align test-patch with this > change. I'm hoping Allen will take point on this, but ping me if I can be > of any assistance. > > On Thu, May 12, 2016 at 11:53 AM, Li Lu <[email protected]> wrote: > >> I’d like to bring YARN-4977 into attention for using Java 8. HADOOP-13083 >> does the maven change and in yarn-api there are ~5000 javadoc warnings. >> >> Li Lu >> >>> On May 10, 2016, at 08:32, Akira AJISAKA <[email protected]> >> wrote: >>> >>> Hi developers, >>> >>> Before cutting 3.0.0-alpha RC, I'd like to drop JDK7 support in trunk. >>> Given this is a critical change, I'm thinking we should get the >> consensus first. >>> >>> One concern I think is, when the minimum version is set to JDK8, we need >> to configure Jenkins to disable multi JDK test only in trunk. >>> >>> Any thoughts? >>> >>> Thanks, >>> Akira >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
