Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2257
Found the culprit. We must not use the `scala.binary.version` property in
flink artifact names. The property is only for switching Scala dependencies. It
is not resolved by Maven in artifact names during deployment which would give
us artifact names of the form `flink-runtime_${scala.binary.version}`. The
problem is that we set the property in the root pom which can only be deployed
one time. Otherwise all artifacts would depend on Scala...a bit nasty.
The build failures occurred because Maven tried to use the
`flink-runtime_2.11` dependency instead of `flink-runtime_2.10` (which is in
fact the Scala 2.11 version if you use `-Dscala-2.11`). `flink-runtime_2.11`
hadn't been installed previously, causing Maven to download it from the
snapshot repository...
I think we're done with this PR after this. I'm going to run the changes on
Travis and will merge to the master then.
---
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.
---
