When I try to perform a maven release of a multi-module project using the com.google.code.maven-scm-provider-svnjava:maven-scm-provider-svnjava:1.12 provider the subversion checkin step fails with the following error

[INFO] Checking in modified POMs...
[INFO] SVN commit directory: c:\richm\hudson\slave\workspace\mvn-release-test
[JENKINS] Archiving c:\richm\hudson\slave\workspace\mvn-release-test\pom.xml to /var/lib/jenkins/jobs/mvn-release-test/modules/uk.org.oldelvet.test$mvn-release-test/builds/2011-04-04_23-56-44/archive/uk.org.oldelvet.test/mvn-release-test/1.17-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
SVN commit failed.
Command output:
svn: 'c:\richm\hudson\slave\workspace\mvn-release-test\C:' is not a working copy
[INFO] ------------------------------------------------------------------------

The same release from the windows commandline and on linux works fine.

After a bit of investigation I have identified the cause of the problem (and an easy workaround).

Basically it seems that svnkit requires that it be passed the canonical names of files to be passed to it. In my case the path begins "c:" and svnkit confuses this with "C:" and gets confused. I can workaround/fix this easily by altering my windows slave configuration to use a pathname beginning with a capital C and all works fine.

Ideally it would be nice to fix this because the error was confusing and I did have to do quite a lot of investigation in the maven-scm-provider-svnjava code to find some clues as to the problem and the workaround.

I have investigated this using Jenkins 1.405 but know it was present in a few earlier builds.

Attached is a sample maven project that fails along with a full log of a failing build.