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

Jarek Potiuk commented on RAT-352:
----------------------------------

Yeah. It would be really great to have .ratignore files. following the exact 
semantics of .gitignore:
 * Ideally we should be able to add multiple .ratignore files in any folder and 
it will apply to the subtree (merging the .gitignore with higher level ignores
 * It should follow 100% gitignore semantics - negation, sequence of 
processing, exclude by default etc.
 * It should work also in the archives.
 * Also - (somewhat related) .ratconfig might be used to configure options used 
by rat (say ----input-exclude-std GIT) - but that might be a separate ticket 
possibly

 Ideally I would like to do `java -jar rat.jar my_source.tar.gz` and it should 
find all the .ratignore files and .ratconfigure file inside and ignore files / 
apply configuration appropriately 

> Define a .ratignore file and processor (Was: Enable use of wildcard 
> expressions in exclude file)
> ------------------------------------------------------------------------------------------------
>
>                 Key: RAT-352
>                 URL: https://issues.apache.org/jira/browse/RAT-352
>             Project: Apache Rat
>          Issue Type: Improvement
>          Components: Client - cli
>            Reporter: Nicholas Chammas
>            Priority: Minor
>              Labels: low-hanging-fruit
>             Fix For: 1.0.0
>
>
> Due to the widespread use of git, I would find it much more intuitive if 
> .rat-excludes worked like .gitignore. I think most people on the Spark 
> project would agree (though, fair disclosure, I haven't polled them).
> Would it make sense to add a CLI option instructing RAT to interpret entries 
> in the exclude file as wildcard expressions (as opposed to regular 
> expressions) that work more or less like .gitignore?
> This feature request is somewhat related to RAT-265.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to