ascheman opened a new issue, #1430: URL: https://github.com/apache/tooling-trusted-releases/issues/1430
### Context ATR's RAT check runs `apache-rat` with the standard exclude sets and doesn't know a project's own excludes, producing false-positive "unknown license" findings on deliberately-excluded files (concrete example: Maven Resolver Ant Tasks 1.6.1 RC — two `src/test/resources/**/*.txt` fixtures flagged although the project's `apache-rat:check` is green). Discussed on dev@tooling: https://lists.apache.org/thread/1ks8dbdxr2smhf5y0odmoybwvg0dbrq8 — Dave Fisher asked for two issues; this is the ATR side. Companion (producing the file): apache/tooling-atr-maven-plugin#78. ### Proposal When a bare `.rat-excludes` file is present among the uploaded artifacts, pass it to the RAT invocation via `--input-exclude-file <file>` (the file form of the `--input-exclude` options ATR already passes). When absent, behaviour is unchanged. ### Notes * This makes per-project RAT checks accurate for projects that provide the file, without ATR having to find/parse `pom.xml`. * Related: #312 (`.rat-excludes` for the non-RAT licence check, closed), #1426 (check-result UX). -- 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]
