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]
