[MNG-6678] Locked version range to a timestamped snapshot does not work

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.6.0
• Component/s: Artifacts and Repositories
• Assignee: Unassigned
• Reporter: James Nord
• Created: 13/Jun/19 14:34
• Updated: 26/Oct/20 12:12

Description

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.