[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815394#comment-15815394
 ] 

Hadoop QA commented on ZOOKEEPER-2651:
--------------------------------------

+1 overall.  GitHub Pull Request  Build
      

    +1 @author.  The patch does not contain any @author tags.

    +0 tests included.  The patch appears to be a documentation patch that 
doesn't require tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 3.0.1) 
warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/198//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/198//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/198//console

This message is automatically generated.

> Missing src/pom.template in release
> -----------------------------------
>
>                 Key: ZOOKEEPER-2651
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2651
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 3.4.9, 3.5.2
>            Reporter: Christopher Tubbs
>            Assignee: Rakesh R
>             Fix For: 3.4.10
>
>
> Trying to build downstream in Fedora, and discovered that the 3.4.9 release 
> tarball is missing the {{src/pom.template}} file. It is present in the 
> {{release-3.4.9}} tag, so I grabbed it from there to patch downstream.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to