maven-scm and scm providers don't know settings.xml. It's the job of plugins to read it and pass
info to maven-scm, so you should look at maven scm plugin or maven release plugin
Emmanuel
Alejandro Nicolas Mascarell a écrit :
I've checked StarteamScmProviderRepository class and it seems StarTeam
gets the password from the URL as well:
public String getFullUrl()
{
String fullUrl = getUser() + ":";
if ( getPassword() != null )
{
fullUrl += getPassword();
}
fullUrl += "@" + getUrl();
return fullUrl;
}
Could you tell what class/classes look after regarding user/pass
resolution on SCM providers based on settings.xml file?
On 2/1/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
I'm not sure, perhaps in some plugins
Emmanuel
Alejandro Nicolas Mascarell a écrit :
Do you mean that user/password configuration it is not allowed for
Subversion on settings.xml in the current version?
On 2/1/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
if your scm url is : scm:provider:...scm_host:scm_port...
<server>
<id>scm_host:scm_port</id>
<username>your_username</username>
<password>your_password</password>
</server>
if your scm url is : scm:provider:...scm_host...
<server>
<id>scm_host</id>
<username>your_username</username>
<password>your_password</password>
</server>
<server> is generally used for artifact repositories uploads, but it can be
used for all features
that require a server.
I think starteam scm provider is the only one that support it. We'll allow it
for all scm providers
Emmanuel
Alejandro Nicolas Mascarell a écrit :
Where on the settings.xml is it possible to define the user/pass for a SCM
provider? I know about the <server> section. But is it not this for Maven
artifacts repositories? Is it not the <server><id> element used as the
reference from <repositories><repository><id> element?
I'm using maven-release-plugin. Is there a way to know MOJO's paramenters
without browsing source code? Thanks for all! ;)
On 2/1/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
We don't allow password in scm svn url for security reason. It's allowed
in scm cvs url for backward
compatibility.
What is the plugin you want to use with scm url?
Actually, some scm providers can read password from settings.xml, but not
all. We need to
standardize it.
If you can't define svn password by a mojo property (I'm pretty sure you
can), you must register it
by running a svn command from command line like this :
svn --username your_username --password your_password command_to_execute
Emmanuel
Maciej Mastalarczuk a écrit :
Hi Alejandro,
The way I got it working is through connecting to SVN using command-line
tool under the user account that is later used for builds. The username
and
password is then cached somewhere (???). On Windows box it goes into
something like that:
C:\Documents and Settings\maven\Application Data\Subversion
(sorry, in my previous post I wrote it went to home directory; my
mistake).
I've no idea where it would go on Linux, but I am sure it can cache it.
After this SVN will just use cached passwords providing you use the same
user account (or do it for all accounts).
There may be a better way of doing it, but I don't know it :-). This
whole
SVN authentication could probably do with a couple of good howto's.
Hope this helps
Maciej
-----Original Message-----
From: Alejandro Nicolas Mascarell [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 1 February 2006 5:04 PM
To: Maven Users List
Subject: [***SPAM*** Score/Req: 10.4/5.0] Re: SVN url password
I am speaking about the password to connect Subversion SCM, not the
Maven
organization repository. On the URL you can specify the user but not the
password (and probably you won't like to do so), but on the
settings.xmlfile as far as I know it is only possible to specify Maven
component
repository passwords.
Alex
On 2/1/06, Mark Struberg < [EMAIL PROTECTED]> wrote:
Hi Alejandro!
I don't know if u ment this when u mentioned the
settings.xml
But i think u have to use a <server> section there.
This is mostly common for all username/password
thingies like tomcat:deploy and so on.
Try to edit your ~/.m2/settings.xml and insert your
settings according to the following configuration for
tomcat. The svn configuration should be nearly the
same:
<settings>
...
<servers>
<server>
<id>tomcat</id>
<username>myTomcatUser</username>
<password>myTomcatPassword</password>
</server>
</servers>
...
</settings>
you then have to reference the server-id in your
pom.xml:
<plugins>
...
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>tomcat-maven-plugin</artifactId>
<version> 1.0-SNAPSHOT</version>
<configuration>
<server>tomcat</server>
</configuration>
</plugin>
...
</plugins>
best regards,
strub
--- Alejandro Nicolas Mascarell
<[EMAIL PROTECTED]> schrieb:
Does anyone know where is the SCM user password
provided when using SCM url?
As from the specification (and checked on
svnScmProviderRepository class)
the password is not gathered for the URL, as in the
case on CVS. I have
checked whether the password was taken from
settings.xml file but it seems
it is not the case.
Thanks!
Alex
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
