[
https://issues.apache.org/jira/browse/HADOOP-16219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810858#comment-16810858
]
Sean Busbey commented on HADOOP-16219:
--------------------------------------
{quote}
bq. just to be clear, this flies directly in the face of our compatibility
guidelines by being an incompatible change in a minor version release, right?
well it would be, if we didn't explicitly call out JVM EOL as something that
can force an update
{quote}
EOL from who though? Aren't there still folks offering JDK7 releases?
This is going to make things unpleasant for HBase as a downstreamer since we've
been trying to maintain jdk7 on our stable release branch and relying on Hadoop
2 releases is part of how we've done that.
> [JDK8] Set minimum version of Hadoop 2 to JDK 8
> -----------------------------------------------
>
> Key: HADOOP-16219
> URL: https://issues.apache.org/jira/browse/HADOOP-16219
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 2.10.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Attachments: HADOOP-16219-branch-2-001.patch
>
>
> Java 7 is long EOL; having branch-2 require it is simply making the release
> process a pain (we aren't building, testing, or releasing on java 7 JVMs any
> more, are we?).
> Staying on java 7 complicates backporting, JAR updates for CVEs (hello
> Guava!) &c are becoming impossible.
> Proposed: increment javac.version = 1.8
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
