Subversion Scan Fails when SVNKit Encounters A Deleted Revision
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When looking up a revision that has been deleted or when a peg revision is specified, the following is logged:
1
2
3
4
5
6
7
8
9
10
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.
Was this helpful?