[MRESOLVER-333] Distinguish better resolver errors for artifact availability

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.9.6
• Component/s: Resolver
• Assignee: Tamas Cservenak
• Reporter: Tamas Cservenak
• Created: 28/Feb/23 08:21
• Updated: 16/Mar/24 08:37
• Resolved: 01/Mar/23 07:46

Description

Improve resolver emitted errors to detail more about the state (the error) how resolver came up with it. Example issues:

• MNG-5185
• MNG-7001

The "artifact availability check" is widely misunderstood.

Issue Links

• fixes: MNG-5185 Improve "missing dependency" error message when _maven.repositories/_remote.repositories contains other repository ids than requested
• Is contained by: MNG-7715 Upgrade to Maven Resolver 1.9.6
• is related to: MNG-8076 when jar in local repository from other repository id, should not reject but check if it is also available in current repository id context
• is superceded by: MRESOLVER-337 Real cause when artifact not found with repository filtering
• links to: GitHub Pull Request #261