You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tooling.apache.org by "sbp (via GitHub)" <gi...@apache.org> on 2026/10/12 15:41:22 UTC
[I] Review which RAT standard exclusions are used by default (tooling-trusted-releases)
sbp opened a new issue, #1723:
URL: https://github.com/apache/tooling-trusted-releases/issues/1723
We should review the value of `_STD_EXCLUSIONS_EXTENDED`, as per discussion on #1722.
--
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: issues-unsubscribe@tooling.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Review which RAT standard exclusions are used by default (tooling-trusted-releases)
Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #1723:
URL: https://github.com/apache/tooling-trusted-releases/issues/1723#issuecomment-6275042599
@ottlinger I reviewed the exclusion types in `ALL` that we don't have in ATR, and none were convincing candidates. Are there any specific ones you'd like us to add to the list, keeping in mind that we always spell them out and can't use `ALL`? `HIDDEN_FILE` would exclude e.g. `.editorconfig` files, and others which should be subject to audit; and `GRADLE` would skip `build/`, whereas for example httpd 2.4.69 includes `build/rules.mk.in` and subversion 1.15.0 includes `build/ac-macros/*.m4`, for build configuration. The defaults in ATR have to apply to all projects, in all languages and ecosystems.
--
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: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Review which RAT standard exclusions are used by default (tooling-trusted-releases)
Posted by "ottlinger (via GitHub)" <gi...@apache.org>.
ottlinger commented on issue #1723:
URL: https://github.com/apache/tooling-trusted-releases/issues/1723#issuecomment-6127640389
fyi: Merged configuration of exclusions to use ALL instead of the manual enumeration.
ALL includes all available Java enumerations found in [RAT's StandardCollection](https://github.com/apache/creadur-rat/blob/master/apache-rat-core/src/main/java/org/apache/rat/config/exclusion/StandardCollection.java)
As projects may have various build tooling, IDE configuration it could be useful to read this list from upstream/RAT.
--
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: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Review which RAT standard exclusions are used by default (tooling-trusted-releases)
Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp closed issue #1723: Review which RAT standard exclusions are used by default
URL: https://github.com/apache/tooling-trusted-releases/issues/1723
--
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: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Review which RAT standard exclusions are used by default (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #1723:
URL: https://github.com/apache/tooling-trusted-releases/issues/1723#issuecomment-6276017790
About a specific configurations per project there is an issue/idea to unifi configuration at RAT level
https://issues.apache.org/jira/browse/RAT-554
only mention here as reference
--
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: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Review which RAT standard exclusions are used by default (tooling-trusted-releases)
Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #1723:
URL: https://github.com/apache/tooling-trusted-releases/issues/1723#issuecomment-6343605109
@ottlinger I'm going to add a link to every RAT result that will show the exclusions used. If the exclusions come from policy, there will be no header. If they come from an archive's dotfile, there will be a comment to that effect. If they come from a URL, the URL will be shown at the top. In conjunction with the exact command line that we already show in RAT results, and the version, this should make it possible to debug every aspect of RAT runs on ATR.
--
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: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Review which RAT standard exclusions are used by default (tooling-trusted-releases)
Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #1723:
URL: https://github.com/apache/tooling-trusted-releases/issues/1723#issuecomment-6343946842
Resolved by 215187c7a673f25622908c80874159958ab3cb62 and baf0560d20cf965f9dbbaab7b5132a733d31de1b.
--
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: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Review which RAT standard exclusions are used by default (tooling-trusted-releases)
Posted by "ottlinger (via GitHub)" <gi...@apache.org>.
ottlinger commented on issue #1723:
URL: https://github.com/apache/tooling-trusted-releases/issues/1723#issuecomment-6344060368
Thanks @sbp - I'm not really sure if a regular user can extract anything useful from the CLI parameters, but at least there's a way for consumers to start a deeper analysis.
--
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: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Review which RAT standard exclusions are used by default (tooling-trusted-releases)
Posted by "ottlinger (via GitHub)" <gi...@apache.org>.
ottlinger commented on issue #1723:
URL: https://github.com/apache/tooling-trusted-releases/issues/1723#issuecomment-6286769326
RAT's exclusions were requested by downstream clients .... no problem - choose as you see fit. Would it make sense to show RAT's config to the user https://github.com/apache/tooling-trusted-releases/issues/1725 to allow spotting configuration errors for specific projects?
--
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: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Review which RAT standard exclusions are used by default (tooling-trusted-releases)
Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #1723:
URL: https://github.com/apache/tooling-trusted-releases/issues/1723#issuecomment-6323698014
I found that the `ECLIPSE` and `STANDARD_SCMS` options were actually blocking checks in `bin` (`ECLIPSE`), `core`, and `tags` (`STANDARD_SCMS`), and that many projects are using such subdirectories to store code that legitimately should be license checked. Therefore I am removing them from the defaults.
--
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: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org