flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aljoscha Krettek (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-7414) Hardcode scala.version to 2.11 in flink-quickstart-scala
Date Fri, 13 Oct 2017 12:33:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aljoscha Krettek closed FLINK-7414.
-----------------------------------
    Resolution: Fixed

Fixed in 85b2f27067ce2fe5b16b3126c816b27e916477d8

> Hardcode scala.version to 2.11 in flink-quickstart-scala
> --------------------------------------------------------
>
>                 Key: FLINK-7414
>                 URL: https://issues.apache.org/jira/browse/FLINK-7414
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System
>    Affects Versions: 1.4.0
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Blocker
>             Fix For: 1.4.0
>
>
> Currently, the {{scala.binary.version}} of the Scala Quickstart is derived from the {{scala.binary.version}}
of Flink at the time when the Quickstart is built. This means that whatever Scala version
is active when we push the Quickstart takes precedence. Currently, when deploying SNAPSHOT
versions we deploy 2.10 first, then 2.11, i.e. the 1.4-SNAPSHOT Scala Quickstart has Scala
version 2.11. The release script deploys first 2.11 and then 2.10, meaning the final 1.4.0
Scala Quickstart would have 2.10.
> Simply fixing it to the latest supported (by Flink) will circumvent that issue and users
can easily change the Scala version in the Quickstart.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message