You're missing my point. You should specify hte version as 5.9-OV.1 (notice the dash and not a dot). "OV.1" being a qualifier. This is best practice as it will work much better with Maven-related tools sorting the different versions.
On Thu, May 23, 2013 at 5:39 PM, Andy <[email protected]>wrote: > OK, So it's along the lines of what I'd like to do, but for the one > drawback mentioned in the blog http://diplingfh.blogspot.ch/** > 2013/02/how-has-our-release-**process-matured.html<http://diplingfh.blogspot.ch/2013/02/how-has-our-release-process-matured.html>that > is *the *drawback. > > Our project uses several of the dependent modules, and so the version > override has to be consistent across all the snapshot child poms uploaded > to the network repo. > > BTW, to answer Anders, 5.9.OV.1 is our own versioning (i.e, 5.9.OV.2 would > be our next iteration), this is done on a 5.9 snapshot copy using > versions-maven-plugin 1.3.1 - Which works just fine, but requires several > steps that I will just have to automate in some other way. > > Still, many thanks Roger - I'm pretty sure you also seem to want to do > what I am outlining here. > > On 23.05.2013 14:44, Andy wrote: > >> Thanks Roger, >> >> I'll give it a go and let you know. >> >> Andy. >> >> On 22.05.2013 17:47, Roger Brechbühl wrote: >> >>> Hi Andy >>> >>> Have a look here: >>> https://github.com/rotscher/**emerging<https://github.com/rotscher/emerging> >>> >>> On the branches there is the latest version. Should work but is not yet >>> released. >>> >> > ------------------------------**------------------------------** > ------------------------------**------------------------------ > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@maven.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > >
