Jochen Wiedmann wrote: > You didn't tell us, how you are using Rat: > > . Maven Plugin: Use the excludes and/or includes properties, see > > http://creadur.apache.org/rat/apache-rat-plugin/check-mojo.html > > - Ant Tasks: The rat-report task uses a standard Ant fileset to specify files > that are being checked. These can contain nested excludes specifications: > > http://creadur.apache.org/rat/apache-rat-plugin/check-mojo.html
Also an example of using the Ant task for RAT directly (no maven) to provide a separate "excludesfile" file with various patterns to exclude: Re: RAT running nicely against Forrest with excludes http://s.apache.org/jmd -David > On Fri, Aug 10, 2012 at 4:56 PM, Chip Childers > <[email protected]> wrote: > > Hi all, > > > > I'm working with the CloudStack (Incubating) project to sort through > > our licensing issues. Specifically, we are using Rat to help us > > identify source files with missing ASF license headers. > > > > It's a great tool, so let me first extend my thanks to this community > > for creating it! > > > > I'm dealing with a situation now, where I'd like to be able to > > configure Rat to have "accepted exceptions". An example of this is > > that we are storing Debian packaging files in the repo. > > Unfortunately, Debian packaging files for binary packages aren't > > allowed to have any comments in them. Other examples include keys, > > certificates, etc... > > > > Is there a method to tell Rat to exclude certain files in it's analysis? > > > > Thanks in advance for any advice / direction / suggestions. > > > > -chip
