svn: OPTIONS of ‘http://intus002/repos/DVApp/branches/8.14′: authorization failed: Could not authenticate to server: rejected Basic challenge (http://intus002)

Here’s the target from build.xml:

I’m running this on a Ubuntu Linux 9.04 system with Sun’s JDK 1.6.0_14. Any ideas on what I’m doing wrong? Running ’svn update’ from that directory works just fine. Your help would be greatly appreciated.

You’ll likely need to uninstall and reinstall a new version of subversion on your machine. Since svnant relies on javahl, it doesn’t contain all the bits for being a subversion client except for using svnkit. Your javahl is likely too old. Try setting svnkit=”true” to use it for your library as another alternative.

Joshua

Now I am still getting the same error I was hoping would be fixed by this update:

[svn] started …
[svn] failed !
[svn] svn: This client is too old to work with working copy ‘bin’. You need
[svn] to get a newer Subversion client, or to downgrade this working copy.

Was this the kind of error that was supposed to be fixed?

Regards,
Hudson

should have been in an “echo” tag…

However, I have a problem, the variable I was using for the revision number in ant is not getting replaced with the number. This line:

revision=${svn.info.lastRev}
used to produce:

info:
[echo] revision=198600

but now it produces :

info:
[echo] revision=${svn.info.lastRev}

I just have the “svnant.jar” and “svnClientAdapter.jar” files in my ant/lib folder, and to upgrade, I just replaced those two files. Is there something else I need to do to get this to work again?
Regards,
Hudson

thank you for your reply. I already thought of an escaping problem. The commandline Ant’s problem is slightly different from svnant’s.

I’m going to send you more details by e-mail because the blogging software would chagrin me …

Regards,
Horst

From what I can tell you are saying that the double backslash turns into a single slash in your comment, similar to an escape.

I imagine this is only with the command line client? Is that true?

This sounds like a good bug report, if you’d like to proceed at subclipse.tigris.org against subclipse, with the svnant component selected.

Please specify which svn library was being used at the time.

Joshua

I turned around the brackets … Your blogging software was afraid of <property …

Having the

<property name=”commit-comment” value=”something\\” />

then a

<commit dir=”.” message=”${commit-comment}” />

results in a log message

something\” –non-interactive C:\my\path\projects

I simply can get around it with a space:

<commit dir=”.” message=”${commit-comment} ” />

But maybe you are interested.

Regards,
Horst

thank you very much! My first smoke test with a SVN-1.6-Repository worked fine.

Regards,
Horst