You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by andreaTP <gi...@git.apache.org> on 2017/03/23 15:38:42 UTC
[GitHub] zeppelin pull request #2183: [ZEPPELIN-2309] Backport maven and npm repo con...
GitHub user andreaTP opened a pull request:
https://github.com/apache/zeppelin/pull/2183
[ZEPPELIN-2309] Backport maven and npm repo config to 0.7
### What is this PR for?
Backport configuration settings for maven central and npm repository to 0.7.
### What type of PR is it?
Improvement
### What is the Jira issue?
[ZEPPELIN-2309]
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nokia/zeppelin backportConfs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2183.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 #2183
----
commit c50c964edd205d7bd1ca6143bf4536e9ada621ed
Author: Andrea Peruffo <an...@gmail.com>
Date: 2017-03-03T10:44:15Z
[ZEPPELIN-2277] Env variable to configure maven central repo
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.
Improvement
Outline the steps to test the PR here.
* Does the licenses files need update?
* Is there breaking changes for older versions?
* Does this needs documentation?
Author: Andrea Peruffo <an...@gmail.com>
Closes #2093 from andreaTP/mavenRepo and squashes the following commits:
af9accc [Andrea Peruffo] [ZEPPELIN-2277] Env variable to configure maven central repo
commit bf8df5d00a2ff1c55816d65a393666d06cead47c
Author: Andrea Peruffo <an...@gmail.com>
Date: 2017-03-17T09:59:44Z
[ZEPPELIN-2278] Env variable to configure Npm registry
When deploying Zeppelin in private Cloud or within closed networks, it happens that Npm Registry isn't directly reachable, so we want to configure our own proxy/registry otherwise we couldn't fetch dependencies. It is anyhow worth to let user configure npm registry instead of hardcoding the URL.
Improvement
[ZEPPELIN-2278]
* Does the licenses files need update?
* Is there breaking changes for older versions?
* Does this needs documentation?
Author: Andrea Peruffo <an...@gmail.com>
Closes #2150 from andreaTP/npmConfig and squashes the following commits:
56fab25 [Andrea Peruffo] [ZEPPELIN-2278] Env variable to configure Npm registry
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #2183: [ZEPPELIN-2309] Backport maven and npm repo con...
Posted by andreaTP <gi...@git.apache.org>.
Github user andreaTP closed the pull request at:
https://github.com/apache/zeppelin/pull/2183
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #2183: [ZEPPELIN-2309] Backport maven and npm repo config to ...
Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2183
Thanks @andreaTP.
LGTM and merge to branch-0.7 if no further discussions.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #2183: [ZEPPELIN-2309] Backport maven and npm repo config to ...
Posted by andreaTP <gi...@git.apache.org>.
Github user andreaTP commented on the issue:
https://github.com/apache/zeppelin/pull/2183
Sure. 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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #2183: [ZEPPELIN-2309] Backport maven and npm repo config to ...
Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2183
Just merged to branch 0.7. but @asfgit did not automatically closed this PR. @andreaTP could you close this PR manually?
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #2183: [ZEPPELIN-2309] Backport maven and npm repo config to ...
Posted by andreaTP <gi...@git.apache.org>.
Github user andreaTP commented on the issue:
https://github.com/apache/zeppelin/pull/2183
Great! 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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---