Hi Mark,
Mark Struberg wrote on Wednesday, February 14, 2007 8:20 AM:
>> 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]:/ho
> me/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]:/ho
> me/cvsroot:${prjScmModule.Name}/
>
> and specify this property in your modules pom:
> <properties>
> <prjScmModule.Name>differentScmModuleName</prjScmModule.Name>
> </properties>
when I did a research with the release plugin, the SCM section was always
completely replaced if it was declared in the current POM. When I tried to use
an inherited SCM section, the artifactId was always automatically appended, no
matter what. Nevertheless we use the svn provider and the plugin was released
since, so my results might be different and become even outdated.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
