sbp commented on issue #1214: URL: https://github.com/apache/tooling-trusted-releases/issues/1214#issuecomment-4382301871
@clr-apache I tested by downloading the exact archive files in revision [00007](https://release-test.apache.org/revisions/db-jdo/3.3#00007) of your `jdo-3.3` draft release, modifying the `.rat-excludes` files as indicated earlier in this thread, and then uploading them to my own local instance of ATR. The problematic `.gitignore` and `META-INF/services` errors do not appear in the checks output, as desired. Because I could not find modified files in the `jdo-3.3` release (revision 00007, from 15 Apr 2026, is the latest), I assume that you are running RAT checks on modified files locally. Perhaps your invocation of RAT differs from the one that ATR uses? You can see the exact command used in the check by opening the check dropdown on e.g. the [`jdo-3.3-SNAPSHOT-source-release.tar.gz` check results page](https://release-test.apache.org/report/db-jdo/3.3/jdo-3.3-SNAPSHOT-source-release.tar.gz). If you scroll down to `Rat Check` and open the `details` element, then scroll down to `Command`, you'll see the command. Note that ATR has to explicitly pass `.rat-excludes` to RAT, as RAT does not automatically scan for or use this file. If you upload the files to ATR, I will be able to see what ATR makes of them and understand what's going wrong if there are still problems. Otherwise, if you do not want to upload them to ATR for any reason, I would appreciate knowing more about how you invoked RAT to help you to debug this. -- 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]
