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

Hudson commented on HBASE-21990:
--------------------------------

Results for branch branch-1
        [build #706 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/706/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/706//General_Nightly_Build_Report/]


(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/706//JDK7_Nightly_Build_Report/]


(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/706//JDK8_Nightly_Build_Report_(Hadoop2)/]




(x) {color:red}-1 source release artifact{color}
-- See build output for details.


> puppycrawl checkstyle dtds 404... moved to sourceforge
> ------------------------------------------------------
>
>                 Key: HBASE-21990
>                 URL: https://issues.apache.org/jira/browse/HBASE-21990
>             Project: HBase
>          Issue Type: Bug
>          Components: build
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0, 2.0.5, 1.3.4, 2.1.4, 1.5.1, 1.2.12
>
>         Attachments: HBASE-21990.branch-2.0.001.patch
>
>
> Yetus flagging two  badly formatted xml files. Seemingly related are the two 
> filenotfoundexceptions that show in the xml.txt build product. 
> https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/branch-2.0/1399/artifact/output-general/xml.txt
> The complaint is that the xml dtds are not found.
> Indeed they were moved long time ago: 
> https://github.com/checkstyle/checkstyle/issues/1571
> They were supposed to stick around at their old location but that seems to 
> have changed recently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to