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

Philipp Ottlinger commented on RAT-243:
---------------------------------------

Thanks for providing the patch and spotting the issue - 
do you know how to configure eclusions?
This would be a way to fix the issue depending on your project setup.

I assume a static exclusion setup is easier to handle and implement in 
comparison to a more generic registering.

> Add Eclipse Checkstyle hidden file to useEclipseDefaultExcludes
> ---------------------------------------------------------------
>
>                 Key: RAT-243
>                 URL: https://issues.apache.org/jira/browse/RAT-243
>             Project: Apache Rat
>          Issue Type: Improvement
>          Components: maven
>    Affects Versions: 0.11, 0.12
>         Environment: Eclipse Oxygen, Checkstyle Plugin 8.0.0.201707161819
>            Reporter: Matthew Ouyang
>            Assignee: Philipp Ottlinger
>            Priority: Minor
>             Fix For: 0.13
>
>         Attachments: eclipse-cs.patch
>
>
> If you try to configure the Eclipse Checkstyle plugin on any project uses the 
> RAT plugin, then it will fail the apache-rat:check goal automatically.  This 
> is because the Eclipse plugin generates a hidden file (.checkstyle) which 
> will not have the required licence file.  Since this file is not part of the 
> artifact produced, it should be excluded from consideration by RAT.  I used 
> the Maven Clean plugin to reproduce this but any project that uses the RAT 
> plugin will suffice.
> Impact: Cannot use work on projects that depend on the RAT plugin in Eclipse 
> if the Eclipse Checkstyle plugin is used.
> Fix: Add .checkstyle to the list of exclusions.  Build RAT with attached 
> patch and rebuild Clean plugin with it.  This is a short-term fix.  A better 
> fix would be to design a way register exclusions with RAT (eg Eclipse 
> Checkstyle could register .checkstyle).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to