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

stack commented on HBASE-5363:
------------------------------

We already have this.  See our pom:

{code}
        <plugin>
          <groupId>org.apache.rat</groupId>
          <artifactId>apache-rat-plugin</artifactId>
          <version>0.7</version>
            <configuration>
              <excludes>
                <exclude>**/.*</exclude>
                <exclude>**/target/**</exclude>
                <exclude>**/CHANGES.txt</exclude>
                <exclude>**/CHANGES.txt</exclude>
                <exclude>**/generated/**</exclude>
                <exclude>**/conf/*</exclude>
                <exclude>**/*.avpr</exclude>
                <exclude>**/control</exclude>
                <exclude>**/conffile</exclude>
                <exclude>**/8e8ab58dcf39412da19833fcd8f687ac</exclude>
                <!--It don't like freebsd license-->
                <exclude>src/site/resources/css/freebsd_docbook.css</exclude>
              </excludes>
            </configuration>
        </plugin>
{code}

And see the generated report: http://hbase.apache.org/rat-report.html

Here is the issue where I messed w/ this stuff on trunk: HBASE-4647
                
> Add rat check to run automatically on mvn build.
> ------------------------------------------------
>
>                 Key: HBASE-5363
>                 URL: https://issues.apache.org/jira/browse/HBASE-5363
>             Project: HBase
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.90.5, 0.92.0
>            Reporter: Jonathan Hsieh
>
> Some of the recent hbase release failed rat checks (mvn rat:check).  We 
> should add checks likely in the mvn package phase so that this becomes a 
> non-issue in the future.
> Here's an example from Whirr:
> https://github.com/apache/whirr/blob/trunk/pom.xml line 388 for an example.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to