[
https://issues.apache.org/jira/browse/MNG-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379949#comment-17379949
]
Robert Scholte commented on MNG-7185:
-------------------------------------
Let's say you write a library. You add a dependency called 'utils' with a
recommended version, so without bounderies. At compile time this will be the
version to be used.
Now there's an application that wants to use this library, but it also adds
utils with a different version. This is fine, because the library only
specified a recommended version. In case library gave utils a version with
bounderies, the application can only choose a version for utils that fits
within the specified bounderies.
If 'library' specified {{[1.0.0]}} for utils, that's the only allowed version,
application cannot change it.
> 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)
