I can recommend not using version ranges, because they break build
reproducibility. If you use a specific version and a tool like Dependabot or
Renovate to create pull requests for updates, you’ll have a reproducible build
without having to keep an eye out for updates yourself.
Nils.
> Op 27 j
ok
From: [Quipsy] Markus Karg
Sent: Wednesday, July 27, 2022 7:41 AM
To: Maven Users List
Subject: Maven fails to resolve version range for import
I think I found a bug in Maven, but I am not sure. Maybe I am doing something
wrong, so Maven Committers, please
Please see issue
https://issues.apache.org/jira/plugins/servlet/mobile#issue/MNG-4463 and will
be resolved in maven 4 if I'm not mistaken.
On Jul 27, 2022, 7:40 AM -0400, [Quipsy] Markus Karg , wrote:
> I think I found a bug in Maven, but I am not sure. Maybe I am doing something
> wrong, so Mav
I think I found a bug in Maven, but I am not sure. Maybe I am doing something
wrong, so Maven Committers, please judge the following case:
A version range in a dependency like...
org.glassfish.jersey.core
jersey-server
[2.0.0, 3.0.0)
mvn dependency:tree
...results in a correct
