I'm not sure why they wouldn't be cached in the first place. SilkSVN is just a Windows distribution of the Subversion binaries, right? I've seen weird things with SVNKit-based clients where an alternate credentials cache is used, but that doesn't appear to be the case here.
If you continue to run into trouble, I'll try to think of some other troubleshooting steps. But really you should get a Mac :) Justin On Mon, Sep 6, 2010 at 9:40 AM, Mike Müller <[email protected]> wrote: > Hi Justin > > I use SilkSVN. Maybe second commit will work without the "hack" > because - as you said - the credentials are cached by SilkSVN... > > best regards > mike > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On >> Behalf Of Justin Edelson >> Sent: Monday, September 06, 2010 3:36 PM >> To: [email protected] >> Subject: Re: Can't prepare release... >> >> AFAIK, your subversion credentials aren't taken from settings.xml; >> Maven just delegates everything to the Subversion command line client >> which has its own credentials cache. >> >> What subversion client do you use normally? >> >> Justin >> >> On Mon, Sep 6, 2010 at 7:01 AM, Mike Müller <[email protected]> wrote: >> > Hi Carsten >> > >> > Thanxs for the help. I don't why credentials are not taken from my >> > settings.xml so far, but it now works for me... >> > >> > best regards >> > mike >> > >> >> -----Original Message----- >> >> From: Carsten Ziegeler [mailto:[email protected]] >> >> Sent: Friday, September 03, 2010 3:47 PM >> >> To: [email protected] >> >> Subject: Re: Can't prepare release... >> >> >> >> Mike Müller wrote >> >> > Hi >> >> > >> >> > I need some further help to do my first release: >> >> > I ran into troubles when I try to execute >> >> > >> >> > mvn release:prepare >> >> > >> >> > The error below appears: >> >> > [INFO] >> >> > ------------------------------------------------------------------------ >> >> > [INFO] Trace >> >> > org.apache.maven.BuildFailureException: Unable to commit files >> >> > Provider message: >> >> > The svn command failed. >> >> > Command output: >> >> > svn: Commit failed (details follow): >> >> > svn: MKACTIVITY of '/repos/asf/!svn/act/496c5cff-cefb-f248-bafe- >> >> 68f9d94195f5': authorization failed: Could not authenticate to server: >> rejec >> >> > ted Basic challenge (https://svn.apache.org) >> >> > >> >> Hi, >> >> >> >> this looks like your svn credentials are not correctly picked up by >> >> maven. So maybe you have to provide your svn user name and/or >> password >> >> to the maven release plugin. Out of the top of my head I think you can >> >> do this with -Duser=x -Dpassword=y >> >> >> >> HTH >> >> Carsten >> >> -- >> >> Carsten Ziegeler >> >> [email protected] >> > >
