Use Maven ANT tasks.. and then pull the version out of the pom so that you don;t need to keep the version in build.xml
On 25 March 2011 11:32, Thiago Veronezi <[email protected]> wrote: > Ah... I love this list... always learning something new... :O) > But we need to change some non "pom.xml" variables too (like build.xml). > > []s, > Thiago. > > > On Fri, Mar 25, 2011 at 5:20 AM, Stephen Connolly < > [email protected]> wrote: > >> any reason why you didn't just do >> >> mvn versions:set versions:commit -DnewVersion=3.4.0-SNAPSHOT >> >> No need for messy S&R and it "just works"... if it doesn't please file a >> JIRA ;-) >> >> On 25 March 2011 08:15, Jean-Louis MONTEIRO <[email protected]> wrote: >> >> > I changed the version number of the 3.2.x branch to 3.2.0-SNAPSHOT. >> > I did the same (not already commited) with 3.4.0-SNAPSHOT. >> > >> > As you may notice, I used 3 digits instead of two because it looks >> clearer >> > to me and it's easier to search/replace. >> > >> > I don't actually know if someone is against. >> > If so, let me know, so that I can revert all changes on 3.2.x branch and >> > also avoid committing 3.4.0-SNAPSHOT. >> > >> > Jean-Louis >> > >> > -- >> > View this message in context: >> > >> http://openejb.979440.n4.nabble.com/Updating-versions-tp3393418p3404778.html >> > Sent from the OpenEJB Dev mailing list archive at Nabble.com. >> > >> >
