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

stack commented on HBASE-21990:
-------------------------------

I left off a closing '>'. Pushed ANOTHER addendum on branch-2.0 only to see how 
it does.

{code}
diff --git 
a/hbase-checkstyle/src/main/resources/hbase/checkstyle-suppressions.xml 
b/hbase-checkstyle/src/main/resources/hbase/checkstyle-suppressions.xml
index b66b4d5972..ec805405eb 100644
--- a/hbase-checkstyle/src/main/resources/hbase/checkstyle-suppressions.xml
+++ b/hbase-checkstyle/src/main/resources/hbase/checkstyle-suppressions.xml
@@ -1,7 +1,7 @@
 <?xml version="1.0"?>
 <!DOCTYPE suppressions PUBLIC
   "-//Checkstyle//DTD SuppressionFilter Configuration 1.2//EN"
-  "https://checkstyle.org/dtds/suppressions_1_2.dtd";
+  "https://checkstyle.org/dtds/suppressions_1_2.dtd"; >
   <!--
 /**
  * Licensed to the Apache Software Foundation (ASF) under one
{code}

> 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, 
> HBASE-21990.branch-2.0.002.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