SVN path is not a working Copy directory solution

Baidu is a lot of ways to solve the path is not a working copy directory, the only way to find a good solution is http://hi.baidu.com/leige87/item/ B9AFF86D17D6F61CA1CF0FCB this way of saying,

Create a folder in another directory, then cheakout out your project and import it into your eclipse.

--------------------------------------------------------------------------------------------------------------- --------------------------------project is special, cause or not solve the following is the latest solution

SVN FAQs Collection
1 SVN directory structure

In the repository of some famous open source projects, we can usually see three directories such as trunk, branches, tags and so on. Because of the inherent nature of SVN, the directory is not particularly meaningful in SVN, but these three directories exist in most open source projects because these three directories reflect the usual patterns of software development.

Trunk
Trunk is the main branch and is the place where daily development is carried out.

Branches
Branches is a branch. Some of the phased release releases, which can be developed and maintained, are placed in the branches directory. For example, for different user customized version, can also be placed in the branch for development.

Tags
The tags directory is generally read-only, where a staged release is stored and archived only as a milestone version.

To use such a structure, when you build the project repository, you can first build the project folder, set up trunk, branches, tags three empty subdirectories, and then import the project folder along with these three subdirectories to the repository. This starts development in the trunk, using the SVN copy operation when a branch or tag is needed. Where the tags directory needs to be read-only, you can use the Authz file in SVN to control access to the directory as read-only.



2 problems with SVN syncing:
Working copy not locked; This is probably a bug,
Svn:directory ' D:\WORKSPACE\MYZJHK\WEBROOT\WEB-INF\CLASSES\ORG\.SVN ' containing working Copy admin area is missing

Workaround:
Delete the Org directory and then perform a synchronization-update operation.


3 SVN error: Attempted to lock an already-locked dir
/*-------------------------------------------------------------------------*/
When this problem occurs, use the "clean" function, and if not, go directly to the top level directory, then "clean" and then "Update".

Sometimes if you see a package inside a folder without the SVN flag, directly with "Ctrl+delete" manually deleted, and then "clean", the last "update" or "submit".
/*-------------------------------------------------------------------------*/
Subversion1.3.2, when anonymous access is turned on and the Authz feature is used to restrict anonymous access, a check out prompts for lock behavior
/*-------------------------------------------------------------------------*/
Sometimes there are files can not be submitted and updated, there is a lock word hint, so that the solution: first click on the file, then Getlock, then select Steallock, and then release lock can


4 error message
Malformed file
Svn:e:\svn\repository\conf\svnserve.conf:12:option expected
Reason:

There are spaces at the beginning of the configuration file 12 line


5 error message
Attempted to lock an already-locked dir
svn:working copy ' E:\integration\com.svn.practise ' Locked

Reason:

Need to use SVN cleanup lock on last shutdown



6 submitting and updating files in Eclipse is a mistake.

Attempted to lock an already-locked dir
svn:working copy ' F:\workspace\WebFrame\WebRoot\attach\prodrelation ' Locked

After you perform a purge operation, the problem is resolved.

Many operations, such as breaking commits, enter the locked state of the working copy.



7 because these two days frequency of this phenomenon, now basically not afraid of this problem
That's how I solved it:
1 repeated injunctions project members must first synchronize, merge, and submit
2 Always use the clean up command in the parent directory after the operation
3 after resolving the locked problem, when there is a phenomenon that cannot be updated, delete all files under the directory, including. SVN, and check out the same directory once again
4 in short, the operation to standardize, to emphasize the team members start every day, first in eclipse synchronization, when the work, to submit (before submission, first in the folder's right menu, select Group > Clear), to ensure that everyone in the machine before the start is the latest version

Frankly speaking, because of version conflicts, commit conflicts, update failures and so on, delayed a lot of time, but I know the main is not proficient in their own operation of the problem. I believe that as long as I insist, everyone, including my crew, will love this little turtle.

It turns from http://www.myexception.cn/cvs-svn/732550.html.

The current test of the http://www.myexception.cn/cvs-svn/470530.html said the method feels feasible.

SVN FAQ Processing

1.SVN submit times wrong: Path is not a working copy directory

(1) This error is usually reported because the folder or its upper folder is not checkout or update.

When working with SVN on the client, you first checkout the repository to the client from the server and then

Checkout out of the folder to operate.

(2) In this directory, under the. svn folder of the directory, open entries, delete <entry name= "DirName" kind= "dir"/>

2.eclipse svn erase remember password

Delete the files under this folder to

C:\Documents and Settings\administrator\application Data\subversion\auth\svn.simple