Thanks for the quick reply,
but maybe this is not what i want.

as far as i know, the svn repository access is configured in the <scm />
section.
I want to acces a subversion source repository not a maven artifact
repository.
So i configured something like the following to access the server's
subversion repository using ssh:

    <scm>
        <connection>
            scm:svn:svn+ssh://[EMAIL 
PROTECTED]/path/to/repository/<http://scm//[EMAIL 
PROTECTED]/path/to/repository/>
        </connection>
        <developerConnection>
            scm:svn:svn+ssh://[EMAIL 
PROTECTED]/path/to/repository/<http://scm//[EMAIL 
PROTECTED]/path/to/repository/>
        </developerConnection>
        <tag>HEAD</tag>
    </scm>

Which does not work.
I wonder where the password for the ssh connection should be stored, and how
the correct subversion db path could be located (maybe throught the HEAD
tag)?

hope someone knows more about this type of scm configuration.

Uli

2008/2/5, Simon Kitching <[EMAIL PROTECTED]>:
>
> ---- Ulrich Metzger <[EMAIL PROTECTED]> schrieb:
> > Hi list,
> > i tryed to configure the scm settings in a maven 2 pom.xml using ssh to
> > access the remote svn repository.
> > But i could not find any example or documentation how to manage this.
> > Does anybody know if this is possible and if yes, how to set up this
> kind of
> > repository access, when a username and password is required for ssh
> login on
> > the remote machine.
> > I would be interested in a solution which works with Windows and Linux
> > client systems.
>
> I have this in ~/.m2/settings.xml:
>
> <settings>
>   <servers>
>     <server>
>       <id>server1</id>
>       <username>user1</username>
>       <password>pwd1</password>
>     </server>
>
>     <server>
>       <id>server2</id>
>       <username>user2</username>
>       <password>pwd2</password>
>       <privateKey>/home/user2/.ssh/somekey</privateKey>
>     </server>
>   </servers>
> </settings>
>
> where the ids match the id properties of the repository definitions in the
> pom.xml file.
>
> Regards,
> Simon
>

Reply via email to