Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1368
@krystiannowak In the referenced commit, you can see that artifacts are
called _2.10 and dependencies are based on _${scala.binary.version}, which
makes things flexible based on the version of scala being used and required the
project to publish both 2.10 and 2.11 versions of the artifact (or use the
change_scala_version script).
What you are proposing here is that the dependency becomes fixed to 2.10
thus causing issues when using 2.11.
---
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.
---