On 24 Sep 2016, at 1:38, Justin Georgeson wrote: > ’m using the parent version range feature with “[1.1.0,1.2.0)” and it had > been going well. However I wanted to start working on 1.2.0 of the parent, so > I published a 1.2.0-alpha-1 version. And all the projects with te > “[1.1.0,1.2.0)” picked it up. I recognize that this is in keeping with the > implementation that x.y.z-(alpha|beta|…) precedes x.y.z, but it is > unintuitive to me. First in that I’ve stated I don’t want 1.2.0, and second > that once I do release 1.2.0 the projects which were receiving the alpha > builds will not get 1.2.0. I tried with both 3.2.5 and 3.3.9. Can the version > range syntax express the range I want?
We have a standing practise of NEVER releasing .0 releases for this very reason. Our ranges tend to be [1.0.0,2.0.0) but the first version would always be 2.0.1-SNAPSHOT. Thinking about it, I should write an enforcement plugin rule that also traps that. -- Mark Derricutt http://www.theoryinpractice.net http://www.chaliceofblood.net http://plus.google.com/+MarkDerricutt http://twitter.com/talios http://facebook.com/mderricutt
signature.asc
Description: OpenPGP digital signature
