Eclipse operation SVN when breaking the lock file unlock method

In Eclipse, open the package where the file resides, click "clean ", then lock first, then unlock: first select team-lock with your account (most importantly, select the" force unlock "option) and select team-unlock.

SVN cleaning failed and report is not a working copy direct

I don't know about SVN. I can't update and submit it. There is a "block" on it when I submit it.
Call clean up, but there will be an error, report "is not a working copy directory"
So I cut out the file, and then I submit it, and it says, "this is missing, submitted." With respect to OK
I made a mistake with classes, because I didn't want to commit classes to SVN, so I copied them in, and that was it. I don't have to go to SVN

Summary of SVN permission setting and the solution of "no right to open root for editing"

If anonymous user access is not allowed, set

This setting is carried out in svnserve.conf:
Anon - access = none
Auth - access = write
If, anon-access = read, you need to add:

[/]
* = r

Otherwise, an error will appear when using SVN to Checkout: you have no right to open the root for editing.

1. Svnserve supports direction-oriented access control;
2. The permissions are inheritable, so it is necessary to use the form of "* = "to prohibit unauthorized users from accessing certain subdirectories;
3. SVN 1.3.2 and later versions allow operation on subdirectories without the read permission of the parent directory;
4. If it is a Chinese directory, authz must be saved in utf-8 format with no BOM, while the files saved in utf-8 format by notepad in Windows will be added with BOM. Therefore, if you save the code in utf-8 format, when SVN reports the error of "section header expected", most of them are with BOM. Of course, many editors are now able to do this easily, such as ultraedit save as u8-dos, editplus save as utf-8, and open source Notepad++ format convert "convert to utf-8 code (no BOM)".