The specific problem is that Xcode doesn't seem to use that binary at all. Otherwise, it wouldn't be showing the following error (or the error itself is wrong?)
Error: 155021 (Unsupported working copy format) Description: This client is too old to work with working copy '/Users/bryan/Dropbox/Development/ConverterTouch'; please get a newer Subversion client
The working copy was, of course, checked out using svn 1.5.0 from CLI so it seems to be complaining that whatever svn client Xcode is using is not as new as Subversion 1.5.0.
That defaults key didn't seem to make any difference. In face, it wasn't defined at first, but defining it to point to my copy of subversion hasn't changed anything.
On Jul 16, 2008, at 4:53 AM, Jean-Daniel Dupas wrote: Le 16 juil. 08 à 11:28, Bryan Henry a écrit : Hi there Xcode-dev -
Does Xcode 3.x support Subversion 1.5.0, or more generally, does it support using a user-specified svn binary? It seems as if the ability to change the svn binary path has been removed even though it is still mentioned in this article, http://developer.apple.com/tools/subversionxcode.html, about Subversion+Xcode. I do most of my checkouts, commits, merges, and whatnot via CLI but the Compare feature in Xcode is nice to have if it would work. It would seem that Xcode is using its own version, though, because moving the locations of the svn binaries on the system still leaves a functional (but not v1.5.0) subversion in Xcode.
Thanks.
Even if this options is not editable in the GUI, it is always documented in the Xcode preferences references (so it probably works). You may have to use the terminal and 'defaults' to set it :
i didn't try svn 1.5 so I cannot tell you if using it with Xcode works.
|