[p4] Maven2/Continuum/Perforce

[Slava Imeshev]

----- Original Message ----- 
> Have you tried the maven-release-plugin?  I'm currently working with
> it to get our releases automatically changing the version number in
> the pom files (all 40 of them).  I've hit a stumbling block or two,
> but I'm trying to make some progress.

This is a commonly seen task. Using build numbers provided by 
a build management server with templates works well usually. 

For instance, the page below, the distribution file names and the build 
numbers that are part of the in-code version information are created 
this way: http://makeashorterlink.com/?F2E341F1D

Template-based search'n'replace is a part of the core functionality
in Maven.

HTH.

Slava


> 
> On 5/2/06, Zarnes, Todd <Todd_Zarnes at intuit.com> wrote:
> > Anybody building projects with Maven2?  Following the scenario of using
> > -SNAPSHOT for the next version/build of a module and when you create a
> > release candidate you Open for Edit the pom.xml file, drop the -SNAPSHOT
> > and run  mvn clean deploy for that module...then roll the version/build
> > number for the next release and add back on the -SNAPSHOT and Submit the
> > changes back into Perforce.  Got to be an easier way.
> >
> >
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user