Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 66885 invoked from network); 9 Jun 2007 12:57:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Jun 2007 12:57:42 -0000 Received: (qmail 53720 invoked by uid 500); 9 Jun 2007 12:57:45 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 53428 invoked by uid 500); 9 Jun 2007 12:57:44 -0000 Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-users@maven.apache.org Delivered-To: mailing list continuum-users@maven.apache.org Received: (qmail 53412 invoked by uid 99); 9 Jun 2007 12:57:44 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Jun 2007 05:57:44 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [62.193.206.9] (HELO webmail9.amenworld.com) (62.193.206.9) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 09 Jun 2007 05:57:39 -0700 Received: (qmail 7792 invoked from network); 9 Jun 2007 12:57:22 -0000 Received: from 251.52.68-86.rev.gaoland.net (HELO ?127.0.0.1?) (86.68.52.251) by 0 with SMTP; 9 Jun 2007 12:57:22 -0000 Message-ID: <466AA3A5.8010408@venisse.net> Date: Sat, 09 Jun 2007 14:57:09 +0200 From: Emmanuel Venisse User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: continuum-users@maven.apache.org Subject: Re: Using properties in continuum scm module References: <4AA99A4ABD271B4D86710B80538CE20DB0D924@INTMAIL01.es.int.atosorigin.com> In-Reply-To: <4AA99A4ABD271B4D86710B80538CE20DB0D924@INTMAIL01.es.int.atosorigin.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org 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:svn:svn://${subversionUser}:${subversionPass}@192.168.215.37/AME/SubversionTelegestion/telegestion.micronesia/ControlNodosAPI > > scm:svn:svn://${subversionUser}:${subversionPass}@192.168.215.37/AME/SubversionTelegestion/telegestion.micronesia/ControlNodosAPI > > > > > > 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 > ------------------------------------------------------------------ >