Github user necosta commented on the issue:
https://github.com/apache/zeppelin/pull/2349
Thanks @1ambda,
Allow me to disagree :) In my opinion should be: "I hope we have a proxy
option as well as configurations for those URLs"
The advantage of having configurable URLs is that it allows us to setup a
repository manager (like Nexus or JFrog Artifactory) for Zeppelin. Not having
one, has disadvantages like no mirroring (leading to latency in download) and
inability to have it running in a private cloud (the main reason I started
working on this ticket). From what I have seen, the other URLs (maven dep) are
handled already.
I just created pull request https://github.com/apache/zeppelin/pull/2363
attached against ZEPPELIN-2152. Just looking at the unit tests it is now
successfully using proxy env variables.
So, to conclude, I would kindly request review on both pull requests.
Thanks.
P.S. If you still disagree, should we get a 3rd opinion? I think it would
good. Thanks.
---
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.
---
