For some days now Ecplise (Oxygen 4.7.1a) shows me question marker icons at all folders and files in the project explorer.
I figured out that this is caused by a broken SVN synchronization. Eclipse error log shows The SVN synchronization information for 'Project' has become corrupt or does not exist.
I use Subclipse (latest version) from Eclipse market place.
I tried:
removing and reinstalling Subclipse
removing workspace and check out SVN repo again
Still the same problem.
The curious thing is that SVN connection is ok. I can use Tortoise SVN in Windows explorer and SVN command line, but Subclipse in Eclipse does not work.
Any solutions to this?
I had the same. I tried the one thing in the link recommended by howlger, namely:
"Close Eclipse. Open your workspace folder and then navigate to:
.metadata\.plugins\org.eclipse.core.resources\.projects
There will be a folder for each project, each will have a file named .syncinfo
in it. Delete all of these files and restart Eclipse."
It did not help. But then I tried "Add to Version Control". It complained that the project is already under Version Control, but the question mark is gone and everything seems to work OK now.
While loading my workbench in Eclipse with the TFS plugin active, it hangs. Similarily to this:
http://social.msdn.microsoft.com/Forums/vstudio/en-US/85c1d3bc-64c2-4c39-80cb-a210d1ed02a8/tfs-eclipse-plugin-causes-eclipse-to-hang
I removed the com.microsoft folders in plugins, and that fixed the hang on load.
Has anyone else run into this?
I have the same problem, which happens when the initial connection to the TFS server fails (proxy issues, in my case).
Removing the com.microsoft folders in plugins does not work for me, so I remove org.eclipse.core.resources/ in the project's metadata (/.metadata/.plugins).
Note that afterwards it is necessary to reimport the projects (Import... -> Existing Projects into Workspace) and share again on TFS.
Close all eclipse project.
Rename .project file to any other name or move somewhere else, for all projects in the same workspace.
Open workspace in eclipse.
(project/s status will be closed when you open workspace, because messing .project
file)
Rename back or place back .project file while eclipse in open.
Right click on project and click on Open Project.
Get latest from TFS.(if cannot connect to TFS. Check you TFS settings and proxy setting)
Close eclipse and reopen workspace.
I am using subversive (an eclipse plugin) to connect connect to an SVN repository. I have only been using it for several weeks but it has been great.
Whenever I create a new project everything works great (see the left side of the image), the project automatically hooks itself up to svn. When I open a workspace that I had before I installed subversive it does not use the plugin (see the right side of the image).
I have tried numerous things to try to enable the plugin:
I looked under all the options under window -> preferences (especially the team preferences
I looked under all of the properties under the project (right click the project -> select properties)
I deleted the workspace folder and created a new one (and re-imported my project)
I looked at the .project file and compared it to a projec that has the plugin enabled but could not see anything relevant there
How can I enable the plugin? The only way that I have found that works is to checkout the project in a fresh empty folder and then open it in eclipse. I am trying to avoid this since it will take an hour or so to redownload.
Right-click on the project, choose Team - Share project... It should then detect the .svn directories already present and propose you to reuse the SVN information stored inside.
I have used Subclipse, a Subversion plugin for Eclipse, in the past and it has always just worked on install but not now. I added it to my Eclipse Helios and it is not identifying any of my files that are under source control as such. It gives the message "Resource not managed" when I inspect a file I know is managed in the SVN Properties view.
I have verified that SVN is checked under Preferences > General > Appearance > Label Decorations and the settings under Preferences > Team > SVN look reasonable.
I am using Subclipse 1.6.13 and Eclipse 3.6.0.
Any Ideas?
Two of my eclipse projects had some kind of problem, I deleted them from the package explorer (did not delete the project files just removed from package explorer) then imported them back in (File > import) and everything was fine. Nothing to do with helios.
There's some discussion here to the effect that it has to do with Eclipse + user permissions. I can't verify personally, as I haven't fiddled with Helios yet.
That in mind, my answer is: if you aren't using some vital feature of Helios, don't migrate from Galileo (or older) yet.
The quality of the SVN implementation - both Subclipse and Subversive leaves a lot to be desired - the latter being the lesser evil in my experience.
For me the only way to get a folder to be noticed (get the little ? icon) so that 'Add to version control' was working was to 'Right Click > Team > Disconnect' and then delete the .svn folder in the repository, and re-setup SVN through eclipse ('Share project').
I had the same problem with the 'src' directory.
solution:
copy the src directory to some other place, ex: c:\temp.
delete the src directory from eclipse project (via package or
project expl.).
open tortoise SVN (right click/repo browser).
drag & drop (while pressing the Ctrl key) the src directory to the
wanted directory in SVN.
in eclipse do: team/synchronozied, then update.
I've got a working copy checked out with svn; furthermore, I've created a new project in Eclipse that has the root of the working copy as the project's location. I want to be able to do stuff like compare versions from Eclipse. I have Subclipse 1.4.8, but that doesn't seem to give me what I want. Am I doing something wrong?
i have an svn working copy that also is a project in eclipse. after installing the subclipse plugin i had the same problem, the working copy was not recognized as such.
i just managed by chance to get it recognized as an svn working copy by renaming the project in question and then renaming it back to its old name. not very nice, but it did the trick :-)
There is an option when creating a new project, to use an existing source directory:
New project/ new Java Project / Create project from existing source.
Use that, tell it where your source lives, and it should automatically detect if it's a SVN working copy.
I guess this is not possible with Subclipse as it's given in its documentation that, you can only import an existing svn-managed folder under one condition, according to the doc:
"The only requirement is that your
working copy has to also be a valid
Eclipse project."
So, if you have a working copy that is not a complete eclipse project, Subclipse will not connect it to SVN.
You can right click on the root node of your project and select: Team / Share project
Then you choose SVN, let the default settings and it should work fine!
I am answering this after a long time of the question being asked. I ended up here because I was facing the same problem.
My solution was to create an empty .svn folder at the root folder of the project (in the latest version of svn client tortoise all meta-data is at the root folder). Then did an eclipse refresh and voila it did the trick. I am running subclipse core - 1.8.4.
One step that seemed to work for me, that no one has explicitly mentioned yet: I closed and then re-opened the project. I tried the "rename" trick, above, and that didn't work, but perhaps the poster of that answer also closed the project - they didn't detail exactly what steps they went thru to rename it. (I found you don't have to close the project to rename it, but perhaps they did.)
< /rob>
In my case, I couldn't use an existing copy because I checked out the code using a newer version of Subversion on the command-line and Subclipse 1.4 couldn't recognize it. Upgrading and going through the improved "Share Project" menu resolved the problem.
I got this tip from the forums here:
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2380064
I had the same issue and here are the details of the fix.
My Eclipse is "Helios Service Release 1".
I had an SVN checkout on my filesystem, I went to New Java Project, unchecked Use default location, chose the location, went to next step, chose the source folder and said Finish.
The project came up with no disk icon on it. As per few forum posts, right-clicked on the project, went to Team > Share Project, chose SVN, clicked Next, and the option was only to share the files to the SVN Repository for the first time.
I said Cancel, and the option is to make changes to the SVN plug-in settings. Went to Window menu, chose Preferences, browsed Team> SVN. Chose the SVN Connector tab, changed the SVNKit 1.2.3 to SVNKit 1.3.5 and said OK.
Then, right clicked on the project, said Team> SVN, on the next screen, chose the option Use Project Settings and clicked Finish. The disk button came to the project and the SVN URL got displayed on it.
Add the repository to your list of repositories in subclipse by choosing Window->Show View->Other... and choose SVN->SVN Repositories. Put in all the necessary info to connect to the repository.
Next, right click the repository and choose "checkout". If the project doesn't already have an eclipse .project file, you can create a new project from the source. If it already has a .project file, it will import that .project and use that as your eclipse project locally.
It will definitively not work if you use a different version of svn to checkout, that the one that is supported by Eclipse. I had this problem as I used svn 1.6 to checkout but I had an older eclipse version that had only 1.5. Subclipse has its own build-in svn client (Actually, in two flavors if I am not mistaken).
Check that the subclipse version matches the svn client that you used to checkout. You can check the plugin version number for subclipse (Help -> About -> Click on subversion logo) and match it against svn --version
This worked for me:
1) Go to the 'SVN Repository Exploring' perspective and add a folder somewhere above your working copy
2) Close and open the Eclipse projects.
This should then be enough to get them recognized by Subclipse.
I have encountered a similar situation were existing projects would not get associated with the Subversive plugin. Unfortunately, none of the previous suggestions helped (renaming projects etc.). What has helped is removing projects from Eclipse by deleting them -- just the projects from Package Explorer and not the actual directories and files on disc (the deletion prompt has a special checkbox for that, which is unchecked by default) -- and reimporting the deleted projects as existing projects back.
Of course, as mentioned in some of the answers here, the relevant SVN repositories need to be registered with Eclipse before reimporting the projects. Otherwise, there would no repositories to re-associate the projects with.
When you open a versioned project (i.e., a project in SVN working copy) in Eclipse, that was never previously used with Subclipse, you need to perform these steps:
Right-click the project in Project Explorer.
Select Team | Share Project.
At this point Subclipse will tell you that "The project is already configured with SVN repository information". Click Next.
Subclipse automatically recognizes this project as versioned and all the features of the SVN plug-in should become available.