Hi Jörg!
The key difference is that the SCM section is in the
PARENT POM and not in the modules POM. And the parent
pom will not be checked in automatically by the
release plugin if you only make a release:prepare and
release:perform on that single module.
LieGrü,
strub
--- Jörg Schaible <[EMAIL PROTECTED]>
schrieb:
> Hi Mark,
>
> Mark Struberg wrote on Tuesday, February 13, 2007
> 12:38 PM:
>
> > Hi!
> > There is a workaround:
> >
> > Specify a parent pom which holds the SCM
> information.
> > This way, the SCM info replacement will actually
> not
> > be part of your pom.
> >> <scm>
> >> <connection>
> >>
> >
>
scm:cvs:pserver:${cvs.username}:[EMAIL PROTECTED]:/ho
> > me/cvsroot:${project.groupId}/
> >> </connection>
> >> <developerConnection..../>
> >> </scm>
> >
> > We used the project.groupId as CVS module name to
> > unify the handling.
>
> This does not help a lot, since the release plugin
> will modify the URLs with the the expanded values of
> the properties.
>
> - Jörg
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail:
http://mail.yahoo.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
