Martin Letenay schrieb:
>>I do not think there really is an svnAnt team. This is essentially a
>>client adapter issue, so I can probably help. My guess, would pretty
>>certainty, is that this is a PATH issue. Finding the command line is a
>>pretty straightforward thing, If it can't find it, then it has to be
>>PATH. That would be a potential issue for JavaHL too.
>>I would assume that a service would inheir the system path variable for
>>the machine, but I am not sure.
>I just can confirm there's nothing specific in the svnant's code.
>It just calls the client adapter's
>SVNClientAdapterFactory.isSVNClientAvailable(javahl or cmdline).
> if ((javahl) && (isJavahlAvailable())) ...
> else if (isCommandLineAvailable()) ...
> else throw new BuildException("Cannot use javahl nor command line
>The client adapter lookup is really simple - System.loadLibrary() res.
>Runtime.exec() for cmdLine.
>As Mark already pointed out, at the moment I too can only suspect the PATH.
Thank you for answer. In fact, you both were right, it seems Windows is
using the system path even when running with different user account. Why
On the other hand it's a pity that Subversion's setup doesn't write
svn.exe's location into the registry (as usual on Windows). The client
adapter could then use this path instead of relying on the global path
to be set.
Thanks for all
Received on Thu Jun 29 07:23:54 2006