Subversion Scan Fails when SVNKit Encounters A Deleted Revision

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

When looking up a revision that has been deleted or when a peg revision is specified, the following is logged:


ERROR - SVN Error diffing revision 6136
com.cenqua.fisheye.rep.u: org.tigris.subversion.javahl.ClientException: svn: No part of path '/java-cvs-trash/CRM/trunk/Model/src/model/BomllinieView1Impl.java' was found in repository HEAD
at com.cenqua.fisheye.svn.j.a(FishEye-1.3.4-build-233:72)
at com.cenqua.fisheye.svn.diff.i.a(FishEye-1.3.4-build-233:159)
.....
.....
Caused by: org.tigris.subversion.javahl.ClientException: svn: No part of path '/java-cvs-trash/CRM/trunk/Model/src/model/BomllinieView1Impl.java' was found in repository HEAD
at org.tigris.subversion.javahl.JavaHLObjectFactory.throwException(JavaHLObjectFactory.java:435)
at org.tmatesoft.svn.core.javahl.SVNClientImpl.throwException(SVNClientImpl.java:1309).....
.....

Cause

This is due to a SVNKit bug. SvnKit can not see revisions which have been deleted even when a peg revision is specified.

Resolution

Please use the Native Client library in place of SvnKit.

Last modified on Nov 21, 2012

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.