Wow, that may be my problem when doing documentation & releases for
mojo.

If it is, look for more frequent releases from the project soon. ;) 

Kris

-----Original Message-----
From: Aaron Anderson [mailto:[EMAIL PROTECTED] 
Sent: Friday, May 05, 2006 3:00 PM
To: Maven Users List
Subject: Re: svn authentication with m2 release plugin

thanks, 
   
  release:prepare -Dusername=myid =Dpassword=mypassword 
   
  did the trick

Alexandre Poitras <[EMAIL PROTECTED]> wrote:
  There is a mistake there, the plugin uses "username" ("user.name" is
the OS user in Java).

On 5/4/06, Andrew Kreps wrote:
> I'm not using SVN, but on the Maven site I found this:
>
>
> Use a different username in the SCM server than he one in the
operating system:
>
> Run mvn -Duser.name=your_username release:prepare
>
>
> It's on this page:
> http://maven.apache.org/plugins/maven-release-plugin/howto.html
>
> Hopefully that will help.
>
>
> On 5/4/06, Aaron Anderson wrote:
> > I am using subversion for scm and would like to use the m2 release
plugin. I run release:prepare but I always get an "authorization failed"
error from svn. After doing a network trace I can that the svn client is
sending my operating system credentials (!) instead of my subversion
credentials. I did not modify the svn cached credentials setting and can
easily run svn up, co, etc without entering credentials and the
credentials sent are correct.
> >
> > Why is svn not sending the proper cached credentials when run from
the release plugin? Is there a way to specify the scm userID & pwd from
the command line as there was with the m1 release plugin?
> >
> > TIA
> >
> >
>
> ---------------------------------------------------------------------
> 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]

Reply via email to