[FLINK-2940] Deploy multiple Scala versions for Maven artifacts

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9, 0.10.0
• Fix Version/s: 1.0.0
• Component/s: Build System
• Assignee: Maximilian Michels
• Reporter: Maximilian Michels
• Created: 29/Oct/15 10:53
• Updated: 27/Jan/16 10:51
• Resolved: 27/Jan/16 10:51

Description

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..

Sub-Tasks

• Flink scala libraries exposed with maven should carry scala version: Resolved
• Remove Twitter Chill dependency from flink-java module: Resolved
• Skip Maven deployment of flink-java8: Closed