[
https://issues.apache.org/jira/browse/STORM-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343785#comment-15343785
]
ASF GitHub Bot commented on STORM-1920:
---------------------------------------
GitHub user HeartSaVioR opened a pull request:
https://github.com/apache/storm/pull/1508
STORM-1920 version of parent pom for storm-kafka-monitor is set
1.0.2-SNAPSHOT in master branch
* set it back to 2.0.0-SNAPSHOT
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/HeartSaVioR/storm STORM-1920
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1508.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 #1508
----
commit 8f66f8c64fd02fe0417756c25308683fb3f4c7cf
Author: Jungtaek Lim <[email protected]>
Date: 2016-06-22T06:10:16Z
STORM-1920 version of parent pom for storm-kafka-monitor is set
1.0.2-SNAPSHOT in master branch
* set it back to 2.0.0-SNAPSHOT
----
> version of parent pom for storm-kafka-monitor is set 1.0.2-SNAPSHOT in master
> branch
> ------------------------------------------------------------------------------------
>
> Key: STORM-1920
> URL: https://issues.apache.org/jira/browse/STORM-1920
> Project: Apache Storm
> Issue Type: Bug
> Components: build
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
>
> Recent Travis CI builds for pull requests are all failed due to this.
> https://travis-ci.org/apache/storm/jobs/139371381
> Unfortunately it should be hard to find with dev. environment since many of
> us ran "mvn install" on Storm 1.0.x-branch which eventually installed Storm
> 1.0.2 jar. That's why we shouldn't ignore CI bad sign.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
