Victor, my underlying problem with the current GeoServer stable branch pom versioning convention is, why should a branch care if a tag has been created? By using (for example) 2.0.3-SNAPSHOT, developers have a completely unnecessary burden of having to update the branch whenever a release tag is made. But that is the current convention.
I checked and 2.0.3-SNAPSHOT is a valid identifier. This proposal is how Maven now works: http://docs.codehaus.org/display/MAVEN/Versioning Here is the old discussion, the last time I complained about it: ------ Original Message -------- Subject: Re: [Geoserver-devel] 2.0.x SNAPSHOT version? Date: Sat, 28 Nov 2009 03:19:38 +0800 From: Justin Deoliveira <jdeol...@opengeo.org> To: Caradoc-Davies, Ben (E&M, Kensington) <ben.caradoc-dav...@csiro.au> CC: Geoserver-devel <geoserver-devel@lists.sourceforge.net> I don't think we have ever been 100% consistent about this. But in general on the stable branch we have included the patch number in snapshot version numbers. I know others have stated that this looks odd as well. I do find it kind of useful to be able to tell what release stream a snapshot comes from, but it makes it a pain for projects depending on geoserver. Should we propose a change? Ben Caradoc-Davies wrote: > I just noticed that the pom gs.version on 2.0.x is set to > > 2.0.1-SNAPSHOT > > Is this intended? I though that the head of this branch would remain as > > 2.0-SNAPSHOT > > Or did I miss something? > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
