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 220.127.116.11-20190613.140544-1 and the range I tried to use was [18.104.22.168-20190613.140544-1]
in the maven-metadata.xml from the artifact root in the repo I see 22.214.171.124-SNAPSHOT is mentioned, and looking in the maven-metadata.xml for the 126.96.36.199-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.