How to solve common errors reported by the Eclipse SVN plug-in

During the process of learning SVN, you often encounter SVN plug-in problems. This article describes how to often see errors reported by the Eclipse SVN plug-in when installing SVN plug-ins, I hope this article will help you with your learning.

AD:

This section will share with you the Common Errors of the Eclipse SVN plug-in encountered during the installation of the SVN plug-in, this section describes how to handle SVN plug-in errors.

Common Errors reported by the Eclipse SVN plug-in:

1. update-rHEADD:/dev/workforce
Workingcopynotlocked; thisisprobablyabug, pleasereport
Svn: Directory 'd: \ JavaWorkshop \ workforce \ web \ WEB-INF \ classes \ com \. svn 'ininingworkingcopyadminareaismissing this problem is mainly a problem of WEB-INF, it is good to delete the WEB-INF to update it again.

2. SVN users and passwords.
Delete C: \ DocumentsandSettings \ Administrator \ ApplicationData \ Subversion and then perform the operation.
If the TortoiseSVN client is installed, you can also clear user information in it.
--------------------------

Use MyEclipse for Java Development and SVN for version control.

After the code is modified, execute Commit and Update, and the following error is prompted:
Org. tigrissubversionjavahl. ClientException: Workingcopynotlocked; thisisprobablyabug, pleasereport
Svn: Workingcopy 'd: \ temp \ workspace \ BOBO365 \ WebRoot \ WEB-INF \ classes \ com 'ismissingornotlocked

I checked it online for a long time. It turns out that eclipse used the src folder. svn folder also "compiled" to the WEB-INF/classes, and copied. svn stores the version information in the src folder, causing an error during the update.

So how to deal with it? The method provided by the author of the article is not good, and I found another better method:

Open the Project in Eclipse-> Properties-> JavaBuildPath menu, on the "Source" tab in the right panel, add

Enter "**/. svn /**".

That is to say, exclude the. svn folder from the compilation path so that the above problems will not occur.
----------------------------------

1. The SVN plug-in error occurs when Eclipse uses SVN for version control and updates:

Use MyEclipse for Java Development and SVN for version control. After the code is modified, execute Commit and Update, and the following error is prompted:

Org. tigrissubversionjavahl. ClientException: Workingcopynotlocked; thisisprobablyabug, pleasereport
Svn: Workingcopy 'd: \ temp \ workspace \ BOBO365 \ WebRoot \ WEB-INF \ classes \ com 'ismissingornotlocked
I checked it online for a long time. It turns out that eclipse used the src folder. svn folder also "compiled" to the WEB-INF/classes, and copied. svn stores the version information in the src folder, causing an error during the update.
So how to deal with it? The method provided by the author of the article is not good, and I found another better method:
Open the Project in Eclipse> Properties> JavaBuildPath menu. On the "Source" tab in the right panel, add "**/. svn/**" to Excluded /**".
That is to say, exclude the. svn folder from the compilation path so that the above problems will not occur.

2. svn 'ininingworkingcopyadminareaismissing has been using SVN for version control. The environment is:

Win2003 + myeclipse6 + svn1.46
Deploy to tomcat5.5 and weblogic8.1

Problem description:
During the eclipse development process, automatic compilation and publishing are often performed. As a result, the. svn folder corresponding to the related folder under the/web-inf/directory is deleted together, And the svn 'ininingworkingcopyadminareaismissing prompt appears during synchronization.

Solution:
Browse the directory structure of the SVN repository, delete all or part of the related files under the/web-inf/directory under the project directory (here I only delete the classes directory), and refresh. And then perform synchronization. OK.
----------------------------------------------------------------

When the local project is compared with the SVN server, a problem such as.../project name/bin/org/. svn... containingworkingcopyadminareais missing occurs:

Bin directory (that is, the directory generated by class should not be used as the svn supervision object), right-click Project-> team-> set attribute-> name: svn: ignore content: bin;

Delete the bin directory in the svn repository;

Delete org from the bin directory locally, right-click the bin directory, update, and then the bin directory disappears;

Clean and build the project again. This section describes the SVN plug-in errors.