Hello, I think you can’t publish ranges to central, but yes if a dependency has a range each built will resolve the Version new, and unless there is a mother dependency fixing the version you get the latest one in that range from your repo.
As others said, just don’t use ranges. Gruss Bernd -- http://bernd.eckenfels.net ________________________________ Von: Creager, Greg <greg.crea...@hp.com.INVALID> Gesendet: Thursday, April 14, 2022 5:37:21 PM An: Maven Users List <users@maven.apache.org> Betreff: RE: Determine Maven Dependencies after a build Another question, if the published pom has a range: Published pom: <dependency> <groupId>com.hp.cp.dfe.shared</groupId> <artifactId>common-types</artifactId> <version>[1.0,1.1)</version> </dependency> Does that mean when another maven build that depends on this will select the latest available common-types in that range, not the one that was used for that build? (my hunch is yes, constant moving target) -----Original Message----- From: Nils Breunese <n...@breun.nl> Sent: Thursday, April 14, 2022 2:01 AM To: Maven Users List <users@maven.apache.org> Subject: Re: Determine Maven Dependencies after a build Alexander Kriegisch <alexan...@kriegisch.name> wrote: > A personal note: I am trying to keep my hands off version ranges. I am > not sure the assumed flexibility is worth the trouble of using it and > running into the same issues as you. It also potentially creates a > huge matrix of possible dependency version combinations which might or > might not play nice with each other. How can you ensure to run your > tests on all of them? Sometimes, there is a bug which affects you in > 2.5.3, but not in 2.5.2, and quickly fixed in 2.5.4. Maybe you did or > did not notice that it even exists. Then suddenly, someone uses the > buggy version, and the software does not work despite green tests. I would indeed also recommend to not use version ranges, and using a tool like Dependabot or Renovate to keep your dependencies up-to-date. Nils. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
