[jira] [Commented] (MNG-6678) Locked version range to a timestamped snapshot does not work

["Michael Osipov (Jira)" <ji...@apache.org>]

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

Michael Osipov commented on MNG-6678:
-------------------------------------

I must excuse, you are of course right. You have chosen a fixed version, and not a floating one. Here is your failure: https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/MNG-6678/1/testReport/. I don't know why that isn't covered yet. This class hasn't been touched for years.

> Locked version range to a timestamped snapshot does not work
> ------------------------------------------------------------
>
>                 Key: MNG-6678
>                 URL: https://issues.apache.org/jira/browse/MNG-6678
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.6.0
>            Reporter: James Nord
>            Priority: Major
>
> I had built and deployed a snapshot to our internal repo mananger (nexus) and then attempted to force the use of that artifact in a downstream project by using an explicit version range for that artifact.
> However when I tried to do this maven complained the version range could not be satisfied.
> for example the snapshot deployed with timestamp {{2.176.1.3-20190613.140544-1}} and the range I tried to use was {{[2.176.1.3-20190613.140544-1]}} 
> in the {{maven-metadata.xml}} from the artifact root in the repo I see 2.176.1.3-SNAPSHOT is mentioned, and looking in the {{maven-metadata.xml}} for the 2.176.1.3-SNAPSHOT I do see it contains that in the list of {{snapshotVersions}}
> This appears to be to be a bug that the versionRange does not correctly identify a timestamped version as a SNAPSHOT and thus resolve the metadata for the snapshot correctly to see what versions of that SNAPSHOT are available.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)