CFBlog Administrator Blog

I've been working on an update for a client site which involves the cleanup of a bunch of unnecessary files in scores of directories under subversion control. In order to ensure the files were deleted properly, I used CFDIRECTORY, along with CFEXECUTE, to safely remove those files from both my development machine and from the SVN repository like this:

<cfloop list="#uselessFiles#" index="i">
<cfif fileExists(directoryPath & "/" & i)>
<cfexecute name="svn" arguments="delete --force #directoryPath#/#i#"></cfexecute>
</cfif>
</cfloop>

My machine was running on SVN version 1.4.1, however the JavaHL bindings (which are used by Subeclipse) which were distributed for that version were only compatible up to Subversion 1.2. This meant that when I used the terminal or CFEXECUTE to manipulate files under SVN control, Subeclipse compatibility on the directories with affected files was lost.

One potential solution for this problem was modifying the Workspace Preferences > Team > SVN preferences to select SVNKit as it's interface rather than the JavaHL bindings. On Leopard, however the SVNKit uses the Keychain for SVN authentication. This would be fine for most, however I use password protection on my OS X Keychain, however, which meant that SVNKit required me to enter my keychain password whenever a connection to the SVN server was made. While not critical, this solution made working with Subeclipse cumbersome - unless I chose to remove the keychain password.

It turns out, however, that the most recent Subversion binary for OSX, 1.4.4 (full list of binaries for Win/Linux), includes an updated version of the JavaHL bindings.

After downloading and installing the 1.4.4 update Subeclipse, using JavaHL as it's SVN interface, now has full compatibility with Subversion 1.4. This means I can use the command line again, and in this particular case CFEXECUTE, without fear of breaking compatibility with Subeclipse, which is definintely worth the upgrade!