[
https://issues.apache.org/jira/browse/FLINK-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels closed FLINK-2940.
-------------------------------------
Resolution: Fixed
As of {{66b4420934ce3d30e4b3476bfcc5c3183de4f405}} we deploy multiple Scala
artifacts through the release script.
> Deploy multiple Scala versions for Maven artifacts
> --------------------------------------------------
>
> Key: FLINK-2940
> URL: https://issues.apache.org/jira/browse/FLINK-2940
> Project: Flink
> Issue Type: Improvement
> Components: Build System
> Affects Versions: 0.9, 0.10.0
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Fix For: 1.0.0
>
>
> Flink implicitly defaults to Scala 2.10 at the moment. For 0.10 we already
> built Scala 2.11 artifacts but did not deploy them in the Maven repository.
> For the 1.0 release, multiple Scala versions should be offered via Maven.
> The artifacts which depend on a version of Scala, should contain the Scala
> version in the artifact name. This is a common convention for Scala
> artifacts. For example, {{flink-scala}} should be renamed to
> {{flink-scala_2.10}} and there should be a {{flink-scala_2.11}} artifact as
> well.
> Scala dependencies should be avoided where possible. For instance,
> {{flink-java}} depends on Chill which depends on a specific version of Scala.
> So we would have {{flink-java_2.10/11}}. We can either try to get rid of the
> Scala dependency for these modules or shade our version of Scala..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
