Re: Plans of moving towards JDK7 in trunk

To summarize the thread so far: a) Java7 is already a supported compile- and runtime environment for Hadoop branch2 and trunk b) Java6 must remain a supported compile- and runtime environment for Hadoop branch2 c) (b) implies that branch2 must stick to Java6 APIs I wonder if point (b) should be r

Re: Plans of moving towards JDK7 in trunk

On 5 April 2014 11:53, Colin McCabe wrote: > I've been using JDK7 for Hadoop development for a while now, and I > know a lot of other folks have as well. Correct me if I'm wrong, but > what we're talking about here is not "moving towards JDK7" but > "breaking compatibility with JDK6." > +1 > >

Re: Plans of moving towards JDK7 in trunk

I've been using JDK7 for Hadoop development for a while now, and I know a lot of other folks have as well. Correct me if I'm wrong, but what we're talking about here is not "moving towards JDK7" but "breaking compatibility with JDK6." There are a lot of good reasons to ditch JDK6. It would let u

Build failed in Jenkins: Hadoop-Common-trunk #1090

See Changes: [acmurthy] YARN-1898. Addendum patch to ensure /jmx and /metrics are re-directed to Active RM. [kihwal] HDFS-6159. TestBalancerWithNodeGroup.testBalancerWithNodeGroup fails if there is block missing after balancer su