You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/06/07 21:19:00 UTC
[jira] [Resolved] (SPARK-7733) Update build, code to use Java 7 for
1.5.0+
[ https://issues.apache.org/jira/browse/SPARK-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-7733.
------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Issue resolved by pull request 6265
[https://github.com/apache/spark/pull/6265]
> Update build, code to use Java 7 for 1.5.0+
> -------------------------------------------
>
> Key: SPARK-7733
> URL: https://issues.apache.org/jira/browse/SPARK-7733
> Project: Spark
> Issue Type: Task
> Components: Build, Deploy, Spark Core
> Reporter: Sean Owen
> Assignee: Sean Owen
> Fix For: 1.5.0
>
>
> Following the announced intention to drop Java 6 support in Spark 1.5, we should go ahead and switch master to Java 7 for Spark 1.5. We can also then remove a few checks and comments that were specific to supporting Java 6.
> I think we might also usefully use the try-with-resources feature to improve / tighten up resource management in Java code, and look at replacing some uses of Guava functions with new JDK equivalents.
> It's probably not quite worth replacing {{List<String> foo = new ArrayList<String>()}} with {{List<String> foo = new ArrayList<>()}} everywhere but that simplification might be useful to apply over time as the Java code is otherwise changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org