Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2257
https://s3.amazonaws.com/archive.travis-ci.org/jobs/146612227/log.txt
After checking the logs again, I know why Maven isn't using the installed
`flink-runtime` artifact. It tries to download the `flink-runtime_2.11`
artifact when, in fact, it should try to download `flink-runtime-2.10`. Note,
that the build is a Scala 2.11 build but this should only set the Scala version
of dependencies but not change any Flink artifact names (we have a another
script for that). When flink-runtime is built, it is built with Scala 2.11
although named flink-runtime_2.10. Still, `flink-yarn` attempts to download
`flink-runtime_2.11`.
Trying to dig deeper, why this could be the case.
---
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.
---
