Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2285
> in some other cases you might want spark interpreter to spark 2.2 and
livy interpreter to spark 1.6
In that case, in both approaches we all have to create a new profile in
livy module. And we can't name as spark-1.6, we need to give it a different
name (like livy-spark-1.6). I mean when user specify profiles in maven build
command, all the profiles in root module and sub moduels are in the same scope
and they should have unique name.
---
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.
---
