Do you also skip even releases to keep never have 2.2.0 < 2.2-SNAPSHOT ? This would mean: 3.0.0-SNAPSHOT 3.0.1 3.0.2-SNAPSHOT 3.0.3 3.1.0-SNAPSHOT 3.1.1 ...
That's not a bad idea either ;-) On Mon, Feb 7, 2011 at 09:11, Mark Derricutt <[email protected]> wrote: > We've gotten into the habit of NEVER having .0 releases EVER. > > i.e. we always start with 2.0.1-SNAPSHOT, or 1.3.4.1-SNAPSHOT. This way a > range of [2.0,3.0) works nicely. > > -- > "Great artists are extremely selfish and arrogant things" — Steven Wilson, > Porcupine Tree > > On Mon, Feb 7, 2011 at 9:06 PM, Guillaume Nodet <[email protected]> wrote: > >> In OSGi, 2.2-SNAPSHOT > 2.2.0, so it can cause artifacts to be badly >> wired against the snapshot instead of the release. So you can't >> really deploy snapshots and releases at the same time. >> On the other hand, it you build an artifact that import >> > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
