Troubleshoot common Eclipse SVN plugin error methods _java

Source: Internet
Author: User
Tags svn

In the process of learning SVN, you often encounter SVN plug-in problem, this article describes the installation of the SVN plugin common Eclipse SVN plugin error information problem, I hope this article will help you learn.

AD:

This section looks at the common Eclipse SVN plugin error information that the SVN plugin encountered during the installation, and share it with you, hoping that this section will show you what to do when the SVN plugin complains.

Common Eclipse SVN plugin error information:

1, Update-rheadd:/dev/workforce
Workingcopynotlocked;thisisprobablyabug,pleasereport
Svn:directory ' D:\JavaWorkshop\workforce\web\WEB-INF\classes\com\. SVN ' containingworkingcopyadminareaismissing This problem is mainly Web-inf, it's OK Web-inf to delete and update it again.

2, SVN change the user, password problems.
Remove the C:\DocumentsandSettings\Administrator\ApplicationData\Subversion and then operate on it.
If the TORTOISESVN client is installed, you can also clear the user information inside.
--------------------------

Use MyEclipse for Java development and version control with SVN.

Execute a commit after the code has been modified, and then update, prompting you to follow a similar error:
Org.tigrissubversionjavahl.clientexception:workingcopynotlocked;thisisprobablyabug,pleasereport
Svn:workingcopy ' D:\temp\workspace\BOBO365\WebRoot\WEB-INF\classes\com ' ismissingornotlocked

Search on the internet for a long time, the original is eclipse to the SRC folder. SVN folder is also "compiled" into the web-inf/classes, and copied over. The version information in the SRC folder is stored in SVN, causing an error in the update.

So how to deal with it, the author of the article is not a good way, I found a better way:

Open the Project->properties->javabuildpath menu in Eclipse, and in the right panel, the Source tab, add the excluded

into "**/.svn/**".

Which is to exclude the. SVN folder from the compilation path, so that the above problem does not occur.
----------------------------------

1.Eclipse version control with SVN the SVN plugin error problem encountered while performing the update:

Use MyEclipse for Java development and version control with SVN. Execute a commit after the code has been modified, and then update, prompting you to follow a similar error:

Org.tigrissubversionjavahl.clientexception:workingcopynotlocked;thisisprobablyabug,pleasereport
Svn:workingcopy ' D:\temp\workspace\BOBO365\WebRoot\WEB-INF\classes\com ' ismissingornotlocked
Search on the internet for a long time, the original is eclipse to the SRC folder. SVN folder is also "compiled" into the web-inf/classes, and copied over. The version information in the SRC folder is stored in SVN, causing an error in the update.
So how to deal with it, the author of the article is not a good way, I found a better way:
Open the Project->properties->javabuildpath menu in Eclipse and add "**/.svn/**" to the excluded in the right panel on the Source tab.
Which is to exclude the. SVN folder from the compilation path, so that the above problem does not occur.

2.svn ' containingworkingcopyadminareaismissing has been using SVN for versioning, and the environment is:

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

Problem Description:
The eclipse development process is often automatically compiled and published, which results in the corresponding folders in the/web-inf/directory. SVN folders are removed, causing synchronization to occur: SVN ' Containingworkingcopyadminareaismissing hint.

Solution:
Browse the SVN warehouse directory structure and delete all or part of the related files in the corresponding/web-inf/directory in the engineering directory (here I just delete the classes directory) and refresh. Then do the sync work, OK.
----------------------------------------------------------------

When the local project is compared to the SVN server, it produces .../project name/bin/org/.svn.....containingworkingcopyadminareais missing solution:

Should not put the bin directory (that is, the class generated directory as SVN supervision object), right key item-"team-" Set Properties-"Name: Svn:ignore content: Bin;

Remove the bin directory from the SVN warehouse;

Locally remove org from bin directory, then right-click bin directory, update, then bin directory disappears;

Clean and build the project again. This section describes the SVN plugin error issue.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.