Re: [nant-dev] Nant svn export

2005-06-10 Thread Marcin Hoppe
On 6/8/05, Jennifer Brandon [EMAIL PROTECTED] wrote: I am attempting to perform a svn export using the nant svn task but I get the following error: INTERNAL ERROR System.NullReferenceException: Object reference not set to an instance of an object. at

Re: [nant-dev] Nant svn export

2005-06-10 Thread Marcin Hoppe
On 6/10/05, Marcin Hoppe [EMAIL PROTECTED] wrote: What version of NAnt are you using? This issue should be fixed in CVS for quite some time. One more comment: this error most probably means that you don't have svn.exe in your PATH. NAnt's svn task requires svn.exe client utility to be visible

Re: [nant-dev] Nant svn export

2005-06-10 Thread Vincent Chu
Maybe if you run nant again with debug on (-debug+) and send us the output, it'd help us pinpoint the problem ? vince Jennifer Brandon wrote: Hi I am attempting to perform a svn export using the nant svn task but I get the following error: INTERNAL ERROR System.NullReferenceException:

Re: [nant-dev] Nant svn export

2005-06-10 Thread Marcin Hoppe
On 6/10/05, Vincent Chu [EMAIL PROTECTED] wrote: Maybe if you run nant again with debug on (-debug+) and send us the output, it'd help us pinpoint the problem ? A few weeks ago a similar problem appeared (it thrown a NullReferenceException when svn.exe was not available) on the user/dev list

Re: [nant-dev] Nant svn export

2005-06-10 Thread Vincent Chu
task! Thanks Jenny -Original Message- From: Marcin Hoppe [mailto:[EMAIL PROTECTED] Sent: 10 June 2005 11:23 To: Vincent Chu Cc: Jennifer Brandon; nant-developers@lists.sourceforge.net Subject: Re: [nant-dev] Nant svn export On 6/10/05, Vincent Chu [EMAIL PROTECTED] wrote: Maybe

Re: [nant-dev] Nant svn export

2005-06-10 Thread Marcin Hoppe
On 6/10/05, Vincent Chu [EMAIL PROTECTED] wrote: If you didn't have svn.exe in your path, it would definitely cause a NullReference error right after your last path is searched. No, it's already fixed in CVS. If svn.exe is not on the PATH, there should be a fancy error message instead of ugly