cstamas commented on issue #11423: URL: https://github.com/apache/maven/issues/11423#issuecomment-3540969781
The default use case for group filter was "allow none + allow selectively", as explained in [doco](https://maven.apache.org/resolver/remote-repository-filtering.html) and [demo](https://github.com/cstamas/rrf-demo). The whole reason for groupId was in fact to fight against forges exposing their "public" supergroup that among forge things offered central artifacts as well. So the original idea was "prefix is negative (what is for sure not here) and group is positive filter (what G you can get)" and the two nicely supplement each other. But I agree, adding "def rule" is not biggie. -- 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]
