michael-o commented on PR #1095: URL: https://github.com/apache/maven/pull/1095#issuecomment-1519941803
> 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 instead of user. As you listed, there are MANY tricky situations, like lack oof (or wrong) auth credentials, but again, 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 why I have asked. How should be an absent dependency defined? Only not found or anything else too? That is why this is a draft. -- 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
