[ 
https://issues.apache.org/jira/browse/MRESOLVER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605942#comment-17605942
 ] 

Tamás Cservenák commented on MRESOLVER-224:
-------------------------------------------

Yes, MNG-4452 introduced new maven metadata XML model version "1.1.0", as 
original (used by Maven2) has this limitation from beginning. Moreover, some 
MRMs like Nexus transform the served XML based on UA of the client (detects 
Maven2 vs Maven3) UNLESS cached/deployed Maven metadata is v1.0.0...

It has to be examined how 1.0.0 version model XML got in picture at all...

> DefaultVersionResolver is inflicting ArtifactNotFoundException for 
> classifiers with SNAPSHOT version
> ----------------------------------------------------------------------------------------------------
>
>                 Key: MRESOLVER-224
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-224
>             Project: Maven Resolver
>          Issue Type: Bug
>          Components: Resolver
>    Affects Versions: 1.6.3
>            Reporter: Tuomas Kiviaho
>            Priority: Major
>             Fix For: waiting-for-feedback
>
>
> 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.
> {code:java}
> [INFO] [DEBUG] Resolving artifact 
> <mygroupid>.<myartifactid>:jar:<myclassifier>:<mybaseversion>-SNAPSHOT from 
> []{code}
>  



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

Reply via email to