> So long as maven supports your scm...
But then it is still much better to get this SCM supported then having hundred
of developers tweaking around manually.
Which SCM you need isn't supported yet?
Since I already wrote the maven-scm-providers-git, I maybe can help you in
writing another one.
LieGrü,
strub
--- [EMAIL PROTECTED] <[EMAIL PROTECTED]> schrieb am Do, 5.6.2008:
> Mark Struberg <[EMAIL PROTECTED]> wrote on 04/06/2008
> 22:53:35:
>
> > Maybe i missed the point, or you did.
> >
> > The usual behaviour is to always have a SNAPSHOT
> version in your SCM
> > e.g. <version>1.4-SNAPSHOT</version>
> >
> > If you make a build, you simply use the
> maven-release-plugin
> >
> > $>mvn release:prepare
> > this will
> > .) ask you the release-version which will default to
> 1.4 and the next-
> > version which defaults to 1.5-SNAPSHOT
> > .) does some usefull checks
> > .) checkin pom with the 1.4 into SCM and tag the
> project
> > .) set the next version in the pom to 1.5-SNAPSHOT or
> whatever you
> > provided in step 1
> >
> > after this, do a
> > $>mvn release:perform
> > to build the project with the freshly tagged build
> version
> >
> > So there is usually no need to set versions in the pom
> manually.
>
> So long as maven supports your scm...
>
__________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
