You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2023/02/28 16:06:00 UTC

[jira] [Created] (MRESOLVER-335) Better resolver errors for Artifact Not Found

Slawomir Jaranowski created MRESOLVER-335:
---------------------------------------------

             Summary: Better resolver errors for Artifact Not Found
                 Key: MRESOLVER-335
                 URL: https://issues.apache.org/jira/browse/MRESOLVER-335
             Project: Maven Resolver
          Issue Type: Improvement
            Reporter: Slawomir Jaranowski


When we have many remote repositories only first {{ArtifactNotFoundException}} is returned, all checks for other repositories are hidden.

Next case is with remote repository filtering, checks for remote repository according to filtering also produce {{ArtifactNotFoundException}}, this is done at the beginning so exception is first on list.

In logs and exception we have:

{code}
Downloading from my-mirror: https://artifactory.../artifactory/remote-repos/org/apache/commons/commons-lang3/4.4.4/commons-lang3-4.4.4.pom
[WARNING] The POM for org.apache.commons:commons-lang3:jar:4.4.4 is missing, no dependency information available
Downloading from my-mirror: https://artifactory.../artifactory/remote-repos/org/apache/commons/commons-lang3/4.4.4/commons-lang3-4.4.4.jar

[ERROR] Failed to execute goal on project maven-3.9: Could not resolve dependencies for project org.test:maven-3.9:jar:1.0.0-SNAPSHOT: Prefix org NOT allowed from mayrepo (https://artifactory.../artifactory/myrepo/, default, releases+snapshots) 
{code}

As we see artefact was not found in {{my-mirror}}, but in error report we have information about not allowed prefixes - it can be confusing





--
This message was sent by Atlassian Jira
(v8.20.10#820010)