cstamas commented on PR #2188: URL: https://github.com/apache/maven-resolver/pull/2188#issuecomment-6083276828
I am very uneasy on changes like this (and previous #2082) and here is why: prefixes are _usually_ (and are meant) to be resolved from remote, but, there are (may be) cases, when **user wants to provide them manually**, check out the RRF demo: https://github.com/cstamas/rrf-demo/tree/master/.mvn/rrf So in latter case, prefixes now become "advice" only? In other word, in latter case they are "user provided configuration", that Maven may opt to simply ignore/override? Like, I configured it intentionally like this, but will Maven obey or not, is up to some heuristics. We may then want to distinguish, between "user provided" (when content comes from a configured file) and "remotely resolved" (when it comes from remote)? And this is the reason why I was pushing for "black or white": when present, no magic but fully obeyed, or not served (404 or user configures it disabled) and working without it. Essentially, it boils down to one thing: "fix your MRM, it is broken". No magic or heuristic helps here, when software is broken. -- 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]
