Personnally, when I used cvs, I prefered to used ext protocol with ssh because the pserver isn't independant of the user.
If you can't migrate to ext protocol (just need a ssh access on the cvs server), you don't have an other solution that the one you use. You can report a bug on the release plugin to fix it ( http://jira.codehaus.org/browse/MRELEASE) Emmanuel On Fri, Jun 13, 2008 at 3:33 PM, fma-001 <[EMAIL PROTECTED]> wrote: > > Hi, > > I would like to have a mutable user of the cvs-connection, since the > changes > are done of different users. So I tried to do it like this: > <scm> > <connection>scm:cvs:pserver:${CVS_USER}@<CVS-URL></connection> > </scm> > > The ${CVS_USER} is a property in settings.xml. This works fine for the > first > time, but when doing mvn release:clean release:prepare maven substitutes > the > CVS_USER for the current user and checks the pom in like this: > <scm> > <connection>scm:cvs:pserver:<user>@<CVS-URL></connection> > </scm> > > Is there another way to have the CVS user mutable? > > Thanks in advance, > Franz > -- > View this message in context: > http://www.nabble.com/mutable-CVS-User-tp17823535p17823535.html > Sent from the Maven - SCM mailing list archive at Nabble.com. > >
