On Tue, Mar 15, 2011 at 07:42:19AM +1000, Gav... wrote: > A solution could be: > > Allow ASF Buildbot to check your RAT files for you and publish them for > review:
---->8 SNIP 8<---- > RAT reports are usually triggered on a per commit basis so the reports are > pretty upto date right away. Sounds great! :) Our original ambition was to set up something that would be checked just before cutting a release. Running RAT on every commit is definitely better! > No need to have Buildbot do anything else for you, every project is quite > entitled to just have Buildbot do RAT reports for you. I imagine we will be back for more, later, but this is the one we are prepared to ask for now. > Make sure you look at the working project examples of RAT exclude files. [1] > All you need do is maintain your own list of files to exclude from RAT > reports, keep it is svn and Buildbot will do the rest. > > Let me know if you are sold on this idea and I'll set you up. ;) I'm sold. :) Here's our exclusion list: http://svn.apache.org/repos/asf/incubator/lucy/trunk/devel/conf/rat-excludes If we didn't nail it on the first try, I'll keep committing changes until the report comes up clean. :) Cheers, Marvin Humphrey
