[
https://issues.apache.org/jira/browse/FLINK-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975055#comment-15975055
]
ASF GitHub Bot commented on FLINK-5005:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3703
We cannot add any other dependencies to the pom files. Adding "akka" back
will create a conflict with the "flakka" files.
What we can do is wither of the following two options:
- Release "flakka" for Scala 2.12 and then we need to change nothing in
Flink. The flakka code is at https://github.com/mxm/flakka - we can do the
release, you could help up by checking out what needs to be done to use flakka
with Scala 2.12 (if it is at all possible)
- See if we can pull out the dependency as a property ans use "flakka"
int the Scala 2.10 and 2.11 case and use vanilla akka 2.4 in the
java8/scala2.12 case. That would be a lot of Maven hacking, though - if
possible, I would prefer the first variant (less complexity in Flink).
We can also not add more Travis build profiles (builds take too long
already). We need to keep that number as it is and simply select one of these
profiles to use Scala 2.12 rather than for example 2.10.
> 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)
