Uploaded image for project: 'Maven Resolver'
  1. Maven Resolver
  2. MRESOLVER-335

Better resolver errors for Artifact Not Found

    XMLWordPrintableJSON

Details

    Description

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

      When we have errors for many artifacts in one request - list of problematic artifacts is present in message and only first exception for one artifact.

      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:

      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) 
      

      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

      Attachments

        Issue Links

          Activity

            People

              cstamas Tamas Cservenak
              sjaranowski Slawomir Jaranowski
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: