GitHub user andreaTP opened a pull request:
https://github.com/apache/zeppelin/pull/2093
Env variable to configure maven central repo
### What is this PR for?
When deploying Zeppelin in private Cloud or within closed networks, it
happens that Maven Central isn't directly reachable, so we want to configure
our own proxy and do not have to wait for minutes long timeouts when importing
external libraries. It is anyhow worth to let user configure maven central repo
instead of hardcoding the URL.
### What type of PR is it?
Improvement
### How should this be tested?
Outline the steps to test the PR here.
### Questions:
* Does the licenses files need update?
* Is there breaking changes for older versions?
* Does this needs documentation?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andreaTP/zeppelin mavenRepo
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2093.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2093
----
commit 216144fcb6e52fe6db95afdfef4fde68e601ca4e
Author: Andrea Peruffo <andrea.peruffo1...@gmail.com>
Date: 2017-03-03T10:44:15Z
Env variable to configure maven central repo
----
---
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.
---
