Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2285
> we don't want interpreter's profile to locate in a root pom.xml because
that means all other interpreters profiles can be located in a root
Can you explain more ? Shouldn't all modules share the same profile ? e.g.
We have a new module A which also want to use spark-2.1 profile. Then for the
current pom structure he has to copy spark-2.1 profile to his pom file. If he
want to use a different spark 2.1 profile compared to spark module for his
module, then he has to give it a different profile name. Otherwise it would
conflict with spark 2.1 profile in spark module.
---
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.
---
