Hi Simon, No worries, I think I needed the push to get it finished up and checked in. I have only put together the checkout and update tasks, they still need some flushing out but if you want to look at the labeling (or any other commands that you might need) that would be great. I will try to get the checkout/ update finished this week (i.e. with unit tests and documentation, as well as some missing switches).
I am actually sending in the --no-auth-cache command on the commandline. I reversed all of the negative switches to make them easier (IMO) to read. For instance I find it easier to read recursive=true than no-recursive=false. Just for a second opinion do you find the first more readable than the second? Maybe the cache-auth should be switched to auth-cache though, I will chalk the transposition to a late night :-). I will give the new version a try, but my thoughts are that this is by design, or the way the specific repository is setup. I think what might be going on is any access that does not modify the repository ignores the authentication switches, and only when they are needed they are validated. Anyway, just a thought for now and something that I am going to need to set up my own repository to test :-). Cheers, Clayton > -----Original Message----- > From: Simon Protheroe [mailto:[EMAIL PROTECTED] > Sent: May 2, 2004 2:46 AM > To: Clayton Harbour; [EMAIL PROTECTED] > Subject: RE: [NAntC-Dev] Patch for Subversion task > > > Hi Clayton, > > Thanks very much for this. I can't see the changes in cvs yet > but, from the buildfile you attached, they certainly look > like a much more comprehensive overhaul than the patch I > submitted - great job! As I mentioned, I'm happy to > contribute to the Subversion support so let me know what > needs doing and I'll help where I can. > > Regarding the username/password issue - this may be a > credential caching problem. As you know, svn caches > credentials in the user's application data folder by default. > You can override this, but I think you may have a typo in the > code or the buildfile: The appropriate svn argument is > "--no-auth-cache" which I guess corresponds to the > "cash-auth='false'" in your example buildfile. It might be > worth looking there for the problem. > > On the other hand, it could well be a Subversion issue, as > you suggest. Subversion 1.0.2 was released earlier in the > week - does that behave any differently? > > Cheers, > Simon > > ________________________________ > > From: Clayton Harbour [mailto:[EMAIL PROTECTED] > Sent: Sun 02/05/2004 10:07 > To: Simon Protheroe > Subject: RE: [NAntC-Dev] Patch for Subversion task > > > > Hi Simon, > > I have checked in the <svn-update/> and <svn-checkout/> > tasks. The checkout task is nearly complete, just needs a > few unit tests to make sure that everything is working, and a > once over on the documentation. I have also attached a sample > build file that I was using for testing, which I will > eventually make into a unit test. There is also something a > little odd going on with the username/ password I think, but > this might be a subversion issue (i.e. the username/ password > are invalid but I am still allowed to update/ checkout). > Maybe these are not checked by default until a commit is made? > > > Cheers, > > > Clayton > > > > ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id149&alloc_id66&op=click _______________________________________________ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
