Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/477#issuecomment-78311798
The reason why I asked regarding Scala 2.11.6 was because this version is
shown on the scala-lang website next to the download button.
Also, on maven central, you get the impression that it is released:
http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.scala-lang%22%20AND%20a%3A%22scala-library%22
> >Why aren't we adding a _2.11 suffix to the Scala 2.11 Flink builds?
> We can do this, and it certainly makes sense if you want to ship
pre-builds of both versions. With the current setup if you want to use Flink
with 2.11 you have to build and install the maven projects yourself (I'm
blindly following the Spark model here, let me know if you prefer the other
option).
Thats not entirely true: Users have to build Flink with 2.11 themselves and
then Build their project with `-Dscala-2.11` to activate the profile inside our
pom (on `install` maven does not rewrite poms)
So I'm in favor of adding a `_2.11` suffix to all affected Flink artifacts.
But this is really a major change that we really need to discuss on the
mailing list.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
