Hi Flinksters, We have recently committed an easy way to change Flink's Scala version. The question arises now whether we should ship Scala 2.11 as binaries and via Maven. For the rc0, I created all binaries twice, for Scala 2.10 and 2.11. However, I didn't create Maven artifacts. This follows our current shipping strategy where we only ship Hadoop1 and Hadoop 2.3.0 Maven dependencies but additionally Hadoop 2.4, 2.6, 2.7 as binaries.
Should we also upload Maven dependencies for Scala 2.11? If so, the next question arises: What version pattern should we have for the Flink Scala 2.11 dependencies? For Hadoop, we append -hadoop1 to the VERSION, e.g. artifactID=flink-core, version=0.9.1-hadoop1. However, it is common practice to append the suffix to the artifactID of the Maven dependency, e.g. artifactID=flink-core_2.11, version=0.9.1. This has mostly historic reasons but is widely used. Whatever naming pattern we choose, it should be consistent. I would be in favor of changing our artifact names to contain the Hadoop and Scala version. This would also imply that all Scala dependent Maven modules receive a Scala suffix (also the default Scala 2.10 modules). Cheers, Max
