I am using the Eclipse plugin for TFS and it would not let me upload my project file to the TFS folder I created. In an attempt to fix this issue I deleted the folder from TFS.
I am also using Visual Studio 2013 for my C# projects.
After deleting the folder in TFS I am not able to connect to source control from Eclipse and when I log into VS I get an error that says Cannot Reconcile Local Workspace With Server.
I have tried removing all mapping from TFS but when I do it automatically shows back up. I even undeleted the folder that started the issue and still get the same error.
Any one have any ideas?
In my case It solved by doing in IDE==> Eclipse IDE go to help--> Check for Updates--> any Updates regarding to Team foundation server/ Team Server Explorer===> update it and next==> Next==> click to restart ==> close the Eclipse IDE and again open it try to connect to TFS.
We had this problem too under Windows and the solution was to use one workspace per IDE, that is, one for Eclipse and another one for all Visual Studios. This way, the TFS plug-in for Eclipse (Team Explorer Everywhere) doesn't interfere with VS and vice-versa.
I have tried removing all mapping from TFS but when I do it
automatically shows back up. I even undeleted the folder that started
the issue and still get the same error.
When you see strange things like this, you have to clear the TFS client caches:
For Visual Studios:
Close all Visual Studio instances.
Using Windows Explorer:
Browse to folder "%localappdata%\Microsoft\Team Foundation".
Delete all subfolders (or look for subfolders named "cache" and delete them).
I had this issue in Mac machine and using Eclipse for connecting with TFS,
I tried uninstalling eclipse, clearing eclipse cache/files from all these below folders
~/Library/Preferences/
~/Library/Application Support/
~/Library/Caches/ Folders
Still the issue was there & it showed below errors
An internal error occurred during: "Reconciling local TFS workspace".
com.microsoft.tfs.core.clients.versioncontrol.exceptions.PathTooLongException:
ExceptionMessage="The specified path, file name, or both are too long.
The fully qualified file name must be less than 260 characters, and
the directory name must be less than 248 characters."
An internal error occurred during: "Refreshing TFS Repository
information for http://tfs.xyzcompanyname.com:7071/tfs/DN/".
com.microsoft.tfs.core.clients.versioncontrol.exceptions.PathTooLongException:
ExceptionMessage="The specified path, file name, or both are too long.
The fully qualified file name must be less than 260 characters, and
the directory name must be less than 248 characters."
Then I followed and looked for the below file/folder
/Users/xyzusername/Library/Application Support/Microsoft/Team Foundation/4.0/Cache/
VersionControl.config
This file was always showing the Mapped Paths even if I removed them early. I think this is taking from Mac's cache or from some other loaction.
Then I followed the below steps to remove the workspace association and it worked!!
What you have todo is just Open Team Explorer => go to TFVC Pending changes => Click on Actions => Manage Workspace => Add a new Workspace & remove the existing one (Note: If you have any changes that are still there at your local machine you might want to copy them to a different location, this activity will remove any pending tracking in local). I am attaching the screenshots so that it will be helpful for someone who got a similar issue.
Step 1:
Step 2:
Step 3:
I had similar issues and it helped to run Eclipse as Administrator.
I had this same problem in my mac. I deleted all mapped folders and restarted eclipse. Issue resolved.
Related
I have installed a virtual box with Windows 10, Eclipse Mars, Subversive Plugin, SVNKit 1.8.11 and tried to set up some repositories in a configuration I already did successfully in several other environments. The SVN server is a Debian 7 system with Subversion 1.6.17. The following problem occurs only since I set up the above mentioned system:
Check-out: e. g. SVN-Repositories -> expand Repository X -> right-click on trunk -> check-out -> Error occurs: "Checkout operation for 'svn://host/X/trunk' failed. svn: E200030: There are unfinished transactions detected in 'C:\PathToWorkspace\X'"
After this the Subversive plugin stops working, apparently.
Export: same result as check-out
Further investigation got me to a specific file in the repository, which fails loading with "invalid handle" error. It is not in a "strange" path (not too long, no spaces or special characters) and the file itself contains no suspicious characters, just Unix line breaks. Permissions and space on disk are OK. Other respositories with the same properties DO work as expected.
I found posts with similar problems, but none of them applied to mine, apparently. They told me to wipe my workspace directory (which I did), but I just lost all of my settings without solving the problem. After this, I investigated the program directory of Eclipse, whicht didn't bring any more success.
Additionally, the ".svn\wc.db" file is still locked after the failure. Deleting the repository is therefore not possible until closing Eclipse. The directory is not listed in any project list/tree in eclipse like the package explorer, but the directory exists on the disk.
The same repository X still works in every of the other configurations I have. How can I reset these "transactions" in order to repair this? I really would like to avoid completely reinstalling Eclipse or even Windows.
EDIT
I istalled TortoiseSVN 1.16.16.21511 (x64), which perfectly fits to the SVN service version. Same problem.
First, try:
Right-click the project -> Team -> Cleanup.
If that didn't help:
Restart Eclipse -> Team -> Cleanup
I got the same error in my case but in different situation, I was working on the shared folder using both Eclipse and Tortoise SVN, and Eclipse was not able to clean up or do any commit, so I tried to close Eclipse and do clean up from outside using tortoise. it worked.
I finally got it: creating the files "con.cpp" and "con.h" from the project had apparently been rejected by Windows. As far as I remember, "con" is kind of a reserved command or sub command in Windows. Renaming it to something else right in the repository solved the problem.
When you are performing any team operations in eclipse ( such as
commit, update, replace ) and if you cancel the operation in between.
The files involved in the operation are locked.
This is one of the possibilities for the error to appear.
To resolve this in Eclipse.
Right Click on the project -> Team -> Cleanup
If the above process doesn't work
Restart eclipse -> Right Click on the project -> Team -> Cleanup
If this didn't resolve the issue.
Remove these locks explicitly.
Ubuntu
Install svn if you haven't installed.
sudo apt-get install subversion
Then clean the project folder.
svn cleanup /path/to/working-copy
Windows
Get Tortise SVN from this link.
After installing, Right-click on the project folder which is linked to SVN.
There will be an option do SVN cleanup. Click on it. It takes some time to clean up.
Then you are good to go.
This solution worked for me.
i had an error also on the command 'cleanup' on a project, and restarting the eclipse didn't solve.
i had to disconnect the project from svn and re-connect later
I had the same issue, unfortunately, the issue with the device storage running out of memory.
Free up the memory and able to proceed further from the mentioned issue
I have Eclipse Luna with Subversive, and I had two problems to syncronize with the Repository in a Server, E170001 and E20030 (sometines one and sometimes both). My solution was:
1.- In Eclipse: go to to "Window" - "Preferences".
2.- Go to "General" - "Network Connections".
Down, at Proxy Bypass, add de IP of the server where you has the Repository of SVN.
I need help. I was starting to work on a new project in Eclipse and so I decided to rid my package explorer space of any past projects within the IDE. I had 2 projects saved prior to opening the IDE: "new" and "project 1." I proceeded to delete project 1 successfully from the IDE permanently without any issues so I tried to delete "new." "new" was a project directory saved on my desktop and upon deletion within the IDE by right clicking, it deleted random files and folders on my desktop as well as other files I'm not aware of within a second, completely bypassing recycle bin-around 50GB of files. I tried to recover most of the files but they are fragmented and therefore damaged. Is this behaviour normal in Eclipse?
Basically in eclipse when you create a project, you create in a workspace. By default the project gets stored in the work space folder. However you can give a specific directory to save your project
The work space folder will usually have information regarding the projects. In eclipse we have 2 kind of delete. i.e.
1) Logical:- Project will get deleted from work space but there wont be any actual delete of files.
2) Physical:- Complete deletion of project.
I guess you would have opted the second one and the project would be corrupt. May be it had some dependent files outside which got deleted also.
usually when I want to remove the project , I go for soft delete. When I completely want to remove the project then I browse and delete the project folder itself.
You can find other related help regarding Eclipse in
http://help.eclipse.org/indigo/index.jsp
I am using eclipse 3.5.2 with Team Foundation Everywhere plugin (TFS plugin).
I have several blackberry projects in my eclipse workspace which i have successfully added to TFS. However I have found that the BlackBerry_App_Descriptor.xml is not being updated in TFS when i make changes to it.
For example when I change the name and version number of the application TFS see's no change in the file so when I check in the server version is still the old data. We are developing on several machines so having changes i do on my machine not propigate to the others is causing problems.
Does anyone know why this is happening? I can see from visual inspection of the .xml file that it is changing but why does TFS not considered it any different?
I have tried manually 'check out for edit' on the file, then change the name and check it back in. But it sees that there are no changes and disreguards my checkin.
Thanks,
Stephanie
Incase anyone else runs into this, it seems that the eclipse plugin for TFS is having issues with comparing XML files. If i manually change the XML contents and save to disk. Then do 'Compare local with server version' it will say 'files are identical'. What I ended up doing was removing the file from TFS. Doing my edits on a local version then readding it. It gets the updates into TFS so the whole team gets the same version. Wish it would just work though because now everytime we want to change anything in an xml file its a long process instead of being a simple update/checkin
I recently moved my Eclipse workspace directory and now Subclipse complains every time I open a file, dumping to the console something like:
Path is not a working copy directory
svn: '[original (pre-move) directory path]' is not a working copy
No such file or directory
This also happens when I explicitly try to view the history of a file. This persists across SVN cleanups, closing and re-opening Eclipse, etc.
Update, checkin, checkout and so on all seem to work fine, and Tortoise doesn't complain at all, so clearly it's not the SVN metadata that's screwed up, it's some Subclipse-specific metadata. Can anyone tell me how to blow this broken metadata away?
Edited to add: "Team > Disconnect" followed by "Team > Share" doesn't solve the problem.
Edited again to add: I've grepped through the whole .metadata directory and one of the project directories for a unique element of the old path and can't find it anywhere except in .metadata/.log (the error message itself) and some old Findbugs warnings. Very nice.
You need to delete the .syncinfo files. This is easily done (in most cases) by closing and opening Eclipse, however you can also do so manually as in the following:
To delete the cache, close Eclipse. The cache is stored in:
[workspace]/.metadata/.plugins/org.eclipse.core.resources/.projects/PROJECTNAME/.syncinfo
So you can just find and delete all files named .syncinfo in
[workspace]/.metadata/.plugins/org.eclipse.core.resources/.projects
Quoted from this article: http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=868799
I just did a "Team -> Cleanup" and this exact error went away! I also got this error because I moved between machines and the path wasn't the same.
Using Eclipse 3.6 and the Subversion 1.6 plugin.
Update in 2016: Still works perfectly with Eclipse 4.5.2 and Subclipse 1.10.
Edited to add: Nope, spoke too soon. This doesn't fix it. Some files just seem not to exhibit the problem.
The following seems to solve the problem:
Team > Disconnect.
Quit Eclipse.
Blow away .metadata/.plugins/org.tigris.subversion.subclipse.*.
Restart Eclipse.
Team > Share.
Not sure how the old path was actually being stored in the plugin prefs, but it must have been in there somehwere. It's kind of pathetic of Subclipse to store absolute paths, but apparently it is.
There's a bug filed on this, or at least on the same error message. No context. Fifty cents says it gets rejected.
I'm sure there are many causes with different solutions, but I found the one that worked for me at Dan Wilson's blog. Simply remove the offending folders from the workspace (probably saving them if they have new content), update (letting Subversion recreate the folders), then move the contents back into the fresh folders in your workspace.
I got the error when I tried to rename a class by changing the case from DAO to Dao in Eclipse.
I had to rename it to something like Dao2 and then was able to rename it to Dao.
What worked for me:
Do a "refactor - rename" on the project => after that do it again to rename it back to the original name.
I was having the same error message using subclipse with javahl on a project that is out of the workspace directory. Changing to svnKit has resolved my problem.
Hard to say without further information.
Did you move the whole workspace or just the content?
Also, you can try creating new workspace from scratch and check out the whole project again.
Alternatively, you may try deleting the .metadata directory and relink the project again using File -> import -> existing project into workspace and then relink the SVN data through Team -> Share projects (with an 's'), or maybe just do this last bit after first disconnecting the project from SVN.
Right click the project folder : Team -> Update to Head
This will bring back the directory. Delete it again and Commit
In my case I had the folders of the projects in the Project Explorer and just had to reopen the project
For me, this error message was caused by an out-of-date installation of Subclipse, and the underlying SVNKit and JahaHL libraries. I have been using TortoiseSVN outside of Eclipse to manage my project directories, and my recent upgrade to the 1.8.x series of (Tortoise)SVN tools broke my working copies for Subclipse.
All I had to do to fix, was go to Help->"Install New Software..." and click "Add..." to add a new update site. I picked the latest update site for the latest release on http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA and upgraded Subclipse from there.
Then all my existing projects just worked, and I could reconnect to the one I had already tried disconnecting from without problems.
I have the same problem
I had a new project, added it to SVN. Then everything works as normal, until I try and refactor-rename any java file, I get:
move D:/dev/sk_ws/ge-parent/ge-core/src/main/java/com/skillkash/ge/beans/Skbean.java D:/dev/sk_ws/ge-parent/ge-core/src/main/java/com/skillkash/ge/beans/SkBean.java
Path is not a working copy directory
svn: Path 'D:\dev\sk_ws\ge-parent\ge-core\src\main\java\com\skillkash\ge\beans\SkBean.java' is not a directory
Now the SVN URL is:
svn://qnap/share/MD0_DATA/svn/sk/ge-core/trunk
and the repository root is:
svn://qnap/share/MD0_DATA/svn/sk
Obviously just sharing the project then trying to move a file using subclipe does not work - it must be a bug. I have to do all my refactoring outside eclipse, and hand edit all the files which are affected.
checkout the whole project to a temp dir, then I copied the first level .svn directory and replaced my working copy .svn folder with this.
http://blog.itopia.de/directory-svn-containing-working-copy-admin-area-is-missing/275
It woks for me.
I had added a png file to my project, but I got this error trying to rename or delete it. Cleaning and refreshing the project didn't do anything.
I went into the svn Team Synchronizing perspective, right clicked on the file and deleted it. That solved my problem.
Right click on the project and select Teams -> Switch to another Branch/Tag/Revision.
Select the appropriate Branch/Tag/Revision that the project should be tied to and click OK.
Give Eclipse some time to process the changes.
Restart Eclipse for the changes to take affect.
I just got this error when I was trying to update some .java files. The problem was I was trying to update the files but the folder that contains that files didn't exist in the path so when I sync and update the folder it works at the first try.
So, dont try to sync files, try to sync the folder.
Sometime ago I had a similar issue. Seems that Subclipse (or Eclipse) stores the absolute path of your working copies. The cleanest solution is to export again your repository to the new path.
If you have non-committed code, then you can copy it on top of the clean export (without the .svn folder)
I too had this issue and I simply deleted the project from the workspace (leaving the files on the files system in tact).
I then imported an svn project into the workspace.
Import->SVN->Checkout Project From SVN.
I used my existing repository location to pull the files in.
This issue was caused when I changed Eclipse editions and used a Subclipse plug-in that was a version ahead of what I should have used.
I uninstalled the newer version and installed the correct older version and all worked well.
All I am trying to do is to set the Java compiler for my project as 5.0. It is 1.4 by default. When I try to save by pressing OK button I get the following error.
Preferences Save Failed:
Reason:
Exception Occured while saving project preferences:
/com.myproj.reqmanager.ui/.settings/org.eclipse.jdt.ui.prefs.
I never got this error earlier. I mean I have imported this project before and saved preference settings without any problem. Out of nowhere I am getting this problem now.
Like Liam I store my project on Dropbox and use it on two different machines and also got the same error. A simple refresh (select the project and press F5, or rightclick on the project and choose Refresh) did the trick for me, as the resource was out of sync. This is usually displayed (e.g. in the editor when trying to edit a source file), but in the case of preferences you'll have to find that message in eclipse's log:
!MESSAGE Exception occurred while saving project preferences: /Utils/.settings/org.eclipse.jdt.core.prefs.
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: '/Utils/.settings/org.eclipse.jdt.core.prefs'.
This might actually be the issue for both of you, as any external modification to a project will cause this out of sync error, and creating a new workspace or using another eclipse version likely purges eclipse's cache, resulting in an automatic refresh.
If you follow this thread, this can be:
because of the use of Eclipse with a workspace on a network drive (not necessarily your case, but worth mentioning just in case)
because the file is somehow locked (either by another process or by a Version Control System with pessimistic locking). See also bug 130266:
Read-only project files come up a lot when dealing with source control systems (like Perforce) that make the local files read-only until they are "checked out".
Five years later and this still occurs. In my case I moved the .settings folder, saved again (.settings is created automatically) and merged the files manually.
Happens on Android Developer Tools Build: v22.6.2.
Check the project's Properties -> Java Compiler, and make sure the 'Compiler compliance level' is 1.8 or 1.7 instead of 1.4.
If this still fails to remove the error, deleting the .settings folder certainly works.
I had this problem also. I had used two versions of eclipse, one on my home machine (juno) and one on my work machine (indigo). Both shared the same folder using a Dropbox folder. All worked fine until I wanted to make some editor style changes, the settings would not save.
The solution in my case was to update the indigo version to juno on my work machine.
Delete the eclipse project files:
.settings (directory)
.project
.classpath
File -> Import... -> Maven -> Existing Maven Projects