Github user herval commented on the issue:
https://github.com/apache/zeppelin/pull/2480
sounds good, Iâll do that then
_____________________________
From: Felix Cheung
<notificati...@github.com<mailto:notificati...@github.com>>
Sent: Wednesday, July 12, 2017 9:34 AM
Subject: Re: [apache/zeppelin] [ZEPPELIN-1249] build all submodules w/ the
same scala version (#2480)
To: apache/zeppelin
<zeppe...@noreply.github.com<mailto:zeppe...@noreply.github.com>>
Cc: Herval Freire <hervalfre...@gmail.com<mailto:hervalfre...@gmail.com>>,
Author <aut...@noreply.github.com<mailto:aut...@noreply.github.com>>
I realize 2.10 is EOL but as mentioned, from a while back many platforms
are still running only on 2.10. Even Spark still supports 2.10 as of the latest
release 2.2.0 from yesterday. The reason is many enterprises have applications
that cannot be easily migrated to 2.11.
It is possible that some users are only using a small number of
interpreters (as you do) and they need a particular scala version. So instead
of forcing all submodule to always use the same scala version, how about set a
global scala version as the default but each submodule still has its own
spark.scala.version that can be set in the maven command line when building?
â
You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHub<https://github.com/apache/zeppelin/pull/2480#issuecomment-314824983>, or
mute the
thread<https://github.com/notifications/unsubscribe-auth/AAAV6pwoowBIvtcK7sFeNYkcva3qjV-Iks5sNPWAgaJpZM4OTkY9>.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
