sbp commented on issue #1214: URL: https://github.com/apache/tooling-trusted-releases/issues/1214#issuecomment-4371742075
@clr-apache Thanks for the report. I downloaded the source archives and noticed that they both contain `.rat-excludes` files. You can add the files that you want to ignore to those files: ``` **/.gitignore **/META-INF/services/* ``` But, then you may be wondering why we don't just ignore these by default. We actually _do_ ignore `.gitignore` by default, at least, but only when a `.rat-excludes` file is not present. If such a file is present, it would be impossible to turn off any of our default choices, so projects would not have control over what files they ignore. In other words, the presence of a `.rat-excludes` file means that we hand control of what is ignored over to the project. If a `.rat-excludes` file is not present, we use default ignores from RAT's standard ignore collections. We choose a small set of collections, but we defer to the RAT project as to what is in those collections. I was wondering how you normally use RAT. If you run RAT through the Maven plugin, with the plugin defaults, I expect that it will skip `**/.gitignore` but it _won't_ skip `**/META-INF/services/*`, because it uses similar collections to ATR. Therefore, through normal Maven plugin use you would have to add the latter to your custom ignores anyway. It might be reasonable to suggest `**/META-INF/services/*` as a candidate for inclusion in one of their standard ignore collections. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
