You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2017/04/28 14:41:04 UTC
[jira] [Commented] (FLINK-6414) Use scala.binary.version in place
of change-scala-version.sh
[ https://issues.apache.org/jira/browse/FLINK-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988923#comment-15988923 ]
Stephan Ewen commented on FLINK-6414:
-------------------------------------
I think we tried to do that initially, but it was not possible to completely rely on variables.
Can't remember quite why, [~uce] or [~rmetzger] might remember why...
> Use scala.binary.version in place of change-scala-version.sh
> ------------------------------------------------------------
>
> Key: FLINK-6414
> URL: https://issues.apache.org/jira/browse/FLINK-6414
> Project: Flink
> Issue Type: Improvement
> Components: Build System
> Affects Versions: 1.3.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
>
> Recent commits have failed to modify {{change-scala-version.sh}} resulting in broken builds for {{scala-2.11}}. It looks like we can remove the need for this script by replacing hard-coded references to the Scala version with Flink's maven variable {{scala.binary.version}}.
> I had initially realized that the change script is [only used for building|https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/building.html#scala-versions] and not for switching the IDE environment.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)