[
https://issues.apache.org/jira/browse/HADOOP-16219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147109#comment-17147109
]
Ayush Saxena commented on HADOOP-16219:
---------------------------------------
[~ahussein] regarding the guava upgrade, it breaks downstream clients as
[~busbey] said. It did even when upgraded in trunk, as it doesn't maintain
source compatibility, And due to this fact, it wasn't pushed to lower branches,
Steve there mentioned :
bq. what we should always that a release 3.X will work with code built on
releases 3.(X-1), etc
Which will not hold true I guess, if we push it to branch 2.10? And anyway we
can't have some different version in 2.10 and then different downgraded version
in 3.1 and then different in 3.3
Bunch of discussion there at HADOOP-16210, can check there.
> [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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
