[
https://issues.apache.org/jira/browse/FLINK-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961831#comment-15961831
]
ASF GitHub Bot commented on FLINK-5005:
---------------------------------------
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3703
@DieBauer thanks for taking this on! I haven't been using Flink with Scala
but I think this will be important to have for the May release.
The required changes for type inferences are interesting. I'm puzzled why
this would regress. Also, if developers are writing against 2.10 then these
issues will not manifest until integration tests are run (the same problem you
are experiencing).
One other thought: since Scala 2.12 requires Java 8, is it still necessary
to specify `jdk8` when executing the `scala-2.12` profile?
Flink Forward starts Monday so developer activity will be low this week.
@StephanEwen thoughts when you have the chance?
> Publish Scala 2.12 artifacts
> ----------------------------
>
> Key: FLINK-5005
> URL: https://issues.apache.org/jira/browse/FLINK-5005
> Project: Flink
> Issue Type: Improvement
> Components: Scala API
> Reporter: Andrew Roberts
>
> Scala 2.12 was [released|http://www.scala-lang.org/news/2.12.0] today, and
> offers many compile-time and runtime speed improvements. It would be great to
> get artifacts up on maven central to allow Flink users to migrate to Scala
> 2.12.0.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
