cstamas commented on PR #1095: URL: https://github.com/apache/maven/pull/1095#issuecomment-1519748227
Am really unsure about all this: IMHO it is completely enough for resolver to state "unable to resolve GAV" (something that is absent or present in local repo, and that message is already present), instead to go great lengths and try to figure out for use. As you listed, there are MANY tricky situations, like lack or (or wrong) auth credentials, that does NOT guarantee that if fixed, artifact will be resolved. IMHO, we should just increase the level of logged causes (maybe even for all tried repositories) and let user figure out? -- 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-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org