Grzegorz Kossakowski wrote: > > For all artifacts we have version consisting of three numbers that I > interpret as: > > major.minor.patch > > Where patch releases should contain only bug-fixes and small changes > (*no* new futures) so it's both back- and forth-compatible and you are > free to switch to any of x.y.z version where x and y are constants. > > For such releases I would like other artifacts to update their > dependencies ASAP. > > Your example about API change is about increasing minor part and your > arguments are fine, IMHO. > Isn't Maven supposed to support this automatically? If I write a dependency with a version [1.2.0,1.3.0) shouldn't maven search for the best version of the 1.2.0 (for example 1.2.5) series but not the 1.3.0 series? Am I missing something? (which is absolutely possible)
Simone
