> and this implies, that you name your directories
> exactly after your artifactIds ...
>
You are right for our current configuration.
But this is not necessarily stringent. In our parent
pom, we did set the SCM module with the
${project.groupId}.
>
scm:cvs:pserver:${cvs.username}:[EMAIL
PROTECTED]:/home/cvsroot:${project.groupId}/
But this trick also works with other maven properties.
So you may try to have your parent pom like:
>
scm:cvs:pserver:${cvs.username}:[EMAIL
PROTECTED]:/home/cvsroot:${prjScmModule.Name}/
and specify this property in your modules pom:
<properties>
<prjScmModule.Name>differentScmModuleName</prjScmModule.Name>
</properties>
LieGrü,
strub
--- Jörg Schaible <[EMAIL PROTECTED]>
schrieb:
> Mark Struberg wrote on Tuesday, February 13, 2007
> 3:26 PM:
>
> > 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.
>
> and this implies, that you name your directories
> exactly after your artifactIds ...
>
> - Jörg
___________________________________________________________
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]
