I have an SVN repository that I want to access via https username/password authentication. This repository contains some source files and a build.xml file that invokes svn as executable:

<exec executable="svn" dir="${project.SrcDir}" output="${project.ScratchReportDir}/statsvn/svn-log.xml" searchpath="true" >
<arg line="log --xml --verbose" />
</exec>

1) I configure the Hudson job and provide the (user/passwd) authentication data for the repository via <hostname>/hudson/scm/SubversionSCM/enterCredential.
2) I start the job, code is checked out into the workspace, but authentication fails on exec svn from the build.xml.
3) When I check the folder ...\<username>\Application Data\Subversion\auth, I notice there is no saved authentication data.
4) Now, when I manually do a svn update on the Hudson workspace (using e.g. TortoiseSVN), authentication data is stored under ...\<username>\Application Data\Subversion\auth.
5) I again start the job, and now the job completes successfully.

So Hudson and/or SVNKit does not store the authentication data under ...\<username>\Application Data\Subversion\auth.
Is this a bug in Hudson or SVNKit?