[MINVOKER-323] DefaultVersionResolver is inflicting ArtifactNotFoundException for classifiers with SNAPSHOT version

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.5.0
• Assignee: Slawomir Jaranowski
• Reporter: Tuomas Kiviaho
• Created: 17/Nov/21 14:54
• Updated: 12/Feb/23 14:49
• Resolved: 01/Feb/23 13:55

Description

I use classifier artifact along with the artifact itself as a dependency in a Maven Invoker Plugin project. The project that calls the invoker has the artifact itself as a dependency, but no reference to the classifier.

This causes resolving of the maven-metadata.xml for the project itself plus downloading of the dependency artifact.When invoker is called the artifact is already downloaded to the local repo and cached with SNAPSHOT key.

This causes the DefaultVersionResolver to merge the version information of the SNAPSHOT<myclassifier>:jar artifact that is now being resolved with the already downloaded SNAPSHOT key. Since the local version is newer than the repo version the DefaultVersionResolver thinks SNAPSHOT<myclassifier>:jar to be outdated thus overriding it with local repo.

Since the SNAPSHOT<myclassifier>:jar doesn't exist in the local repo there are no remote report left to try the DefaultArtifactResolver fails ultimately to ArtifactNotFoundException since there was no download task.

[INFO] [DEBUG] Resolving artifact <mygroupid>.<myartifactid>:jar:<myclassifier>:<mybaseversion>-SNAPSHOT from []

 

Issue Links

• is related to: MINVOKER-313 Get rid of maven-artifact-transfer
• is related to: MNG-7548 Kill off "legacy" repository metadata support