Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
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
- causes
-
MNG-7770 Implement workaround for MNG-7758/MRESOLVER-335
- Open
-
DOXIASITETOOLS-303 Implement workaround for MNG-7758/MRESOLVER-335
- Closed
- is depended upon by
-
MNG-7758 o.e.aether.resolution.ArtifactResolutionException incorrectly examined when multiple repositories are involved
- Closed
- relates to
-
MRESOLVER-337 Real cause when artifact not found with repository filtering
- Closed
-
MNG-7956 Support resolver changes regarding resolution error
- Open
- links to