The best way (I think) is to don't add properties or username/password in the
scm url for svn.
Possible solutions:
- you can use an anonymous access over http for your checkout (and
authenticated access for checkin)
- add login/password in the svn registry of your server, so svn won't require
it from the user in the future
Emmanuel
Raúl Arabaolaza Barquín a écrit :
Hi all:
I´ve a Project that in it´s pom have a scm defined using properties to indicate
subversión username and password something like this:
<scm>
<connection>scm:svn:svn://${subversionUser}:[EMAIL
PROTECTED]/AME/SubversionTelegestion/telegestion.micronesia/ControlNodosAPI</connection>
<developerConnection>scm:svn:svn://${subversionUser}:[EMAIL
PROTECTED]/AME/SubversionTelegestion/telegestion.micronesia/ControlNodosAPI</developerConnection>
</scm>
How can I specify this properties for the continuum´s scm module to use it?
With the arguments tab in my project I can use it in maven calls but continuum
is not using it in the first checkout and so the checkout command failed ...
I´m using maven 2.0.6 subversion and tortoisesvn 1.4.2 and continuum 1.0.3 into
a windows 2000 machine
Anyone has an idea?
Best regards, Raul
------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail
in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender does
not warrant that this transmission is virus-free and will not be liable for
any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener informacion
confidencial destinada solamente a la(s) persona(s) mencionadas
anteriormente. Pueden estar protegidos por secreto profesional Si usted
recibe este correo electronico por error, gracias de informar inmediatamente
al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
Origin no se hace responsable por su contenido. Su contenido no constituye
ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por
ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus
------------------------------------------------------------------
