sbp commented on issue #1430: URL: https://github.com/apache/tooling-trusted-releases/issues/1430#issuecomment-5036687826
@ascheman Yep, thank you for doing so! But we're interested in what you would prefer as the solution and why. Occasionally we have to balance implementation costs etc. against features, but in general we're looking to support release managers in their work and provide them with what they need. When we discussed this before, we figured that `.rat-excludes` inside archives is more useful because then the scope of the ignores is clearer and, as mentioned, there isn't a mixture of policy and release data inside the archive. But if there's some specific reason why you'd need `.rat-excludes` externally, we'd like to know about it. Since the Maven plugin is being developed, presumably the pattern isn't established yet and emitting a `.rat-excludes` in the archive itself would be possible? But would it be desirable? What are the tradeoffs? -- 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]
