[
https://issues.apache.org/jira/browse/MNG-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220621#comment-17220621
]
James Nord edited comment on MNG-6678 at 10/26/20, 11:05 AM:
-------------------------------------------------------------
> did you test with a wide range of Maven versions, to check if we introduced a
> change?
nope
> we never really said that this specific pattern will be always recognized as
> a snapshot.
as a user I care about being able to reference a specific *unique snapshot*
deployment. If that changes in the future to be `1.2.3-SNAPSHOT_1`/
`1.2.3-SNAPSHOT_2` I will of course have to update any project that references
them and will accept that work. However as they are `SNAPSHOT`s and as they can
be garbage collected - I expect that to be a very small issue in reality;
mainly as this would be used to only fetch a specific SNAPSHOT of something for
testing in a small window of time.
was (Author: jnord_cbs):
> did you test with a wide range of Maven versions, to check if we introduced a
> change?
nope
> we never really said that this specific pattern will be always recognized as
> a snapshot.
as a user I do not care what the format is and nor should I. I care about
being able to reference a specific *unique snapshot* deployment. if that
changes in the future to be `1.2.3-SNAPSHOT_1`/ `1.2.3-SNAPSHOT_2` I will of
course have to update any project that references them, however as they are
`SNAPSHOT`s and as they can be garbage collected - I expect that to be a very
small issue in reality; mainly as this would be used to only fetch a specific
SNAPSHOT of something for testing in a small window of time.
> 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
> Fix For: waiting-for-feedback
>
>
> 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)
