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 2019/02/04 14:57:00 UTC
[jira] [Resolved] (SPARK-26813) Consolidate java version across
language compilers and build tools
[ https://issues.apache.org/jira/browse/SPARK-26813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-26813.
-------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 23724
[https://github.com/apache/spark/pull/23724]
> Consolidate java version across language compilers and build tools
> ------------------------------------------------------------------
>
> Key: SPARK-26813
> URL: https://issues.apache.org/jira/browse/SPARK-26813
> Project: Spark
> Issue Type: Improvement
> Components: Build
> Affects Versions: 2.4.0
> Reporter: Chenxiao Mao
> Assignee: Chenxiao Mao
> Priority: Minor
> Fix For: 3.0.0
>
>
> The java version here means versions of javac source, javac target, scalac target. They could be consolidated as a single version (currently 1.8)
> || ||javac||scalac||
> |source|1.8|2.12/2.11|
> |target|1.8|1.8|
> The current issues are as follows
> * Maven defines a single property to specify java version (java.version) while SBT build defines different properties for javac (javacJVMVersion) and scalac (scalacJVMVersion). SBT should use a single property as Maven does.
> * Furthermore, it's better for SBT to refer to java.version defined by Maven. This is possible since we've already been using sbt-pom-reader.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org