Hot answers tagged subclipse
Assuming that your repository is divided into branches, trunk and tags, i'd suggest that you create a new tag. Use the "Branch/Tag" command after commiting your work. It makes a copy that is called a tag and is stored (usually) in the "tags" folder.
I finally solved this by deleting both my ~/.eclipse directory and my workspace directory. I then reinstalled the Subclipse and MercurialEclipse plugins and SVN/Mercurial show up as Team Synchronization options.
running following command helped: eclipse -clean
From the JavaHL FAQ : There is currently a bug in the new support for GNOME keyring in Subversion 1.6. It works OK when using the command line, but not when other users of the libraries use it. Until this is fixed, you can workaround the problem by turning off this feature. The solution is to put the line password-stores = in ~/.subversion/config, ...
yes, you need to upgrade your subclipse plugin & svn connectors, either javahl (1.6.x) or svnkit (1.3.x) so they match support your installed subversion (1.6.5). See the project site for the upgrade site URLs if you don't have these already. Or downgrade your ubuntu subversion package, but I would not recommend doing that.
The situation was I was working on a file that someone else deleted under SVN version control. Thats fine as I was only superficially modifying the unit tests in that file. Under eclipse I syned and updated which deleted the file in question. Subsequent use of SVN under eclipse indicated that the file under question no longer existed in version control. ...
Only top voted, non community-wiki answers of a minimum length are eligible