[GitHub] zeppelin pull request #1569: pom.xml change

[hunylee]

Github user hunylee closed the pull request at:

https://github.com/apache/zeppelin/pull/1569


---
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.
---

[GitHub] zeppelin pull request #1569: pom.xml change

[hunylee]

GitHub user hunylee reopened a pull request:

https://github.com/apache/zeppelin/pull/1569

pom.xml change

### What is this PR for?
## pom.xml is plugin version change
- pom.xml
- beam/pom.xml
- cassandra/pom.xml
- flink/pom.xml
- ignite/pom.xml
- r/pom.xml
- scalding/pom.xml
- spark/pom.xml
- spark-dependencies/pom.xml
- zeppelin-display/pom.xml

### What type of PR is it?

[Improvement | Feature | Documentation]
### Todos
- [ ] zeppelin is pom.xml in the plugin version change [ZEPPELIN-1569]
### How should this be tested?

- Is there breaking changes for older versions?



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/hunylee/zeppelin master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/1569.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 #1569


commit 869ee334fe36ab275633e688b569c2910efbf669
Author: hunylee 
Date:   2016-10-30T06:09:18Z

pom.xml change

commit 54343dae5c89d1ca4d8e6d902bef137b58ba5adc
Author: hunylee 
Date:   2016-10-31T07:21:48Z

Version change

commit 8ff2389b743205cb44167b10cd8276f1549d3917
Author: hunylee 
Date:   2016-10-31T08:24:25Z

change




---
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.
---

[GitHub] zeppelin pull request #1569: pom.xml change

[hunylee]

Github user hunylee closed the pull request at:

https://github.com/apache/zeppelin/pull/1569


---
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.
---

[GitHub] zeppelin pull request #1569: pom.xml change

[hunylee]

GitHub user hunylee opened a pull request:

https://github.com/apache/zeppelin/pull/1569

pom.xml change

### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - 
https://zeppelin.apache.org/contribution/contributions.html


### What type of PR is it?
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]

### Todos
* [ ] - Task

### What is the Jira issue?
* Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
* Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. 
[ZEPPELIN-533]

### How should this be tested?
Outline the steps to test the PR here.

### Screenshots (if appropriate)

### 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/hunylee/zeppelin master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/1569.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 #1569


commit 869ee334fe36ab275633e688b569c2910efbf669
Author: hunylee 
Date:   2016-10-30T06:09:18Z

pom.xml change




---
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.
---