Hi Gandh, > On 27. Jul 2024, at 14:06, Gandhirajan N <gandhiraja...@gmail.com> wrote: > > However, the versionRange in root POM could > introduce unpredictability in builds if newer versions introduce breaking > changes
If that were a version range in a dependency: yes -- but this is a different case. However, this particular "version" tag was in the configuration of the lifecycle plugin that tells Eclipse if and when to execute certain goals. And in fact, "version" is not a valid parameter there while "versionRange" is. It tells Eclipse for which versions of a particular plugin the lifecycle configuration applies. And typically you want to have a generously broad version range there so you don't have to update the rules every time you update a Maven plugin. Cheers, -- Richard
