Version ranges are extremely useful for this case: lib 0.2.4 >> 0.3.0 non inclusive where lib has a guaranteed stable API with only non-breaking bug fixes and additions. There are other uses, too. I sincerely hope it's never dropped or broken.
On Mon, Sep 16, 2013 at 10:09 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > On 16 September 2013 08:20, Jörg Schaible <joerg.schai...@scalaris.com > >wrote: > > > Hi Jason, > > > > Jason van Zyl wrote: > > > > > When a release fails like this it is annoying to have to rev back the > > > version of the POM. I'm not sure who flipped the versions in the POM > and > > > while it's a little more visible to see what you're moving toward I > > prefer > > > the pattern of: > > > > > > 3.1-SNAPSHOT --> 3.1.1 --> 3.1-SNAPSHOT --> 3.1.2 --> 3.1-SNAPSHOT > > > > > > I know this may not be obvious to the casual observer as they may think > > > 3.1 is next, but I'm personally fine with that. > > > > That's quite funny, because we did this years ago when we started using > M2 > > and then we were told here in the list it is an anti-pattern, because > 3.1- > > SNAPSHOT is always minor for the dependency resolution than any 3.1.x > > release. > > > > > That was before it was decided that version ranges were a bad plan. If we > were using version ranges then this would indeed be crapulent > > > > - Jörg > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
