GitHub user khalidhuseynov opened a pull request:
https://github.com/apache/zeppelin/pull/2523
[ZEPPELIN-2764] update packages and documentation for ZeppelinHubRepo
storage
### What is this PR for?
update the packages/documentation/links due to migration of domain and
renaming
### What type of PR is it?
Documentation | Refactoring
### Todos
* [x] - update package/class names
* [x] - update config
* [x] - update docs
### What is the Jira issue?
[ZEPPELIN-2764](https://issues.apache.org/jira/browse/ZEPPELIN-2764)
### How should this be tested?
CI pass
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? n
* Is there breaking changes for older versions? n
* Does this needs documentation? n
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/khalidhuseynov/zeppelin fix/ZEPPELIN-2764
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2523.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 #2523
----
commit 934b45e4fbe722b59b17bb133952067469a01d21
Author: Khalid Huseynov <khalid...@gmail.com>
Date: 2017-08-09T06:11:42Z
rename repo packages
commit 25c7620458380410b66293432ecf5479d0f6b54d
Author: Khalid Huseynov <khalid...@gmail.com>
Date: 2017-08-09T07:41:06Z
update links and logs
commit df0f2a01d78389c9b2b48cbf76ee676acb8dbdde
Author: Khalid Huseynov <khalid...@gmail.com>
Date: 2017-08-09T08:11:40Z
rename repo class
commit 6d9f600523c5561b997a04e44702de77282db32c
Author: Khalid Huseynov <khalid...@gmail.com>
Date: 2017-08-09T08:30:25Z
update token naming
commit 0531523bb1e42f59171a50feaf6ce2e591a71353
Author: Khalid Huseynov <khalid...@gmail.com>
Date: 2017-08-09T08:40:35Z
update docs
----
---
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.
---
