[
https://issues.apache.org/jira/browse/MNG-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379606#comment-17379606
]
Michael Osipov commented on MNG-7185:
-------------------------------------
I can reproduce the test case. Please have a look at
{{org.apache.maven.artifact.versioning.VersionRangeTest.testContains()}}. It
describes your test case. I believe the behavior is correct according to the
implementation while the documentation could be better here, imho. It is a
{{recommendedVersion}}. As far as I remember this mechanism is used to resolve
version ranges for dependencies and unless you provide a hard version
{{[1.0.0]}} a selector can exchange it for another.
[~hboutemy], [~rfscholte], am I wrong here?
> Single version range should not match other versions
> ----------------------------------------------------
>
> Key: MNG-7185
> URL: https://issues.apache.org/jira/browse/MNG-7185
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.8.1
> Reporter: Nils Breunese
> Priority: Minor
> Fix For: waiting-for-feedback
>
>
> I would expect a version range for a single version to not contain any other
> versions, but it seems this is not the case, because this test fails on the
> second assertion:
> {code}
> @Test
> void range_with_single_version_should_not_contain_other_version() {
> VersionRange singleVersionRange =
> VersionRange.createFromVersionSpec("1.0.0");
> assertThat(singleVersionRange.containsVersion(new
> DefaultArtifactVersion("1.0.0"))).isTrue();
> assertThat(singleVersionRange.containsVersion(new
> DefaultArtifactVersion("2.0.0"))).isFalse();
> }
> {code}
> Is this a bug, or do I misinterpret what a single version range is? Does
> {{maven-artifact}} have a concept for a version range that only contains a
> single version?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
