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.
Related
I'm running Eclipse Luna on Ubuntu 12.0.4 in VirtualBox with a Windows 8 host and every once in a while, I will boot up Ubuntu and open up Eclipse to find this:
My projects should be listed in the package explorer but it's all empty and whenever I try to import the project again, it says no projects are found.
At this point, I usually go to my workspace folder and delete the .lock file and rebuild the workspace but is there an alternative to this? This error happens every ~5 times I reopen Eclipse and it has become very annoying. Any help will be appreciated!
EDIT: Okay I just tried deleting the .lock file in the .metadata folder in my workspace and I'm still getting the same error. Any suggestions?
EDIT 2: While closing my currently open tabs, I got this error. The projects that were open were Maven projects if that makes a difference.
so I am a little late for the party, but I fixed that on reimporting my projects.
Under File->Import.. you choose General->Import existing Projects into workspace. On the next page you set your workspace directory as the root directory for importing, which will give you a warning like "Some projects already exist in workspace". Ignore this and click finish.
After that all my projects where back in my workspace.
Good luck
To solve this problem, I re-created my workspace and imported my projects again.
Creating a new workspace is done via:
File > Switch Workspace
This is not an optimal solution, but until Eclipse fixes these bugs, this can save you some time trying to debug your current workspace.
I previously had a very small number of Eclipse plugins installed. So, I quickly headed to the Marketplace and installed my plugins.
And yes, Eclipse's downfall is expected. I personally find IntelliJ IDEs much better.
I've been working on an Android project in Eclipse Indigo for a year on a PC that has updates turned off and no new software installed (deliberately to avoid any instability in the java runtime or other installed software).
This morning Eclipse froze and when I killed it in Task Manage, rebooted the PC and restarted Eclipse it failed to launch, saying
"Eclipse failed, Java was started but returned exit code=-805306369”
Googling this I discovered here . . .
http://spacetech.dk/eclipse-failed-java-was-started-but-returned-exit-code-805306369.html
. . . that this is due to a "corrupted workspace". And that I should rename the workspace, create a new empty one, and import the old project into it.
1. What exactly is a "corrupted workspace"? Is there a particular file that's missing or damaged or locked? Can the "corruption" be debugged? A chkdsk didn't show any problems with the disk. I've never had this happen in Visual Studio with C# projects and I do more Windows development than Android.
2. What's the process for importing the old project into the new workspace, and how do I do it without importing the corruption? It's a big project with hundreds of files so I don't want to try to recreate it by hand.
The workspace is a set of configuration files and your projects, though projects can also exist outside of the workspace. The are configuration files for most of the eclipse plugins you have installed, I suspect one of these is causing the problem.
The configuration is stored in a hidden folder in the workspace called .metadata, their is also a log file in this folder called .log. This log file might give you more of a clue as to what has broken.
You can delete (or move it somewhere else) the .metadata folder and eclipse will recreate it next time it's launched. You will then need to reimport your projects and configure eclipse again.
To reimport your projects, use the import wizard from the "File -> Import" menu item. Select the "General -> Existing projects into workspace" wizard. Now click the "Browse" button and find your projects. Select the projects you want to import and click "Finish". Your workspace should now contain your projects again.
I am using Eclipse Juno SR1 Java EE, and checked out code from SVN as an Eclipse project. I am able to click on files in the project to verify everything was ok. The next time I rebooted, I can't see the project in the Project Explorer window.
A few things I checked: The menu item Project > Open Project is greyed out, indicating there are no closed projects. The project's file tree exists in my workspace. Eclipse won't let me create a new project with the same name because one already exists.
This is my first time using Juno, is there some new control that hides projects from view?
"File -> Import -> General -> Existing Projects Into Workspace"
"File -> Import -> Android -> Existing Android Code Into Workspace" doesn't do what you're trying to accomplish (been there...).
Assuming the above lines mean what they say, the first tells Eclipse to recognize what you're importing as an official Project. The 2nd tells Eclipse that you're importing only the code, not the Project itself.
Sometimes it's just because .project file is missing. If you have any other project, copy its .project file and paste inside the main folder of the project you're trying to import.
Try starting with the clean option in command line, maybe that should fix it
eclipse -clean
try
file -> switch workspace -> other
and tell eclipse where your workspace is
I was facing the same problem with RAD. What I did was:
imported only those projects which were deployed locally in my portal server.
Did a clean build.
Started the server.
It worked for me. Able to access my application. Rest of the projects which were not deployed as part of my local portal server, I will import them on need basis later.
I've been using Subclipse to manage SVN projects in Eclipse 3.4.2. However, while installing a buggy plugin, Eclipse became so sluggishly unusable that I had to kill the process and restart. Unfortunately, even though I removed the buggy plugin, this appears to have destroyed Subclipse's links to all my SVN projects. The projects themselves are still there, but the "Team" context menu only shows "Apply Patch", and no SVN icon overlays are being displayed. Is there anyway to fix this, or do I have to delete and recreate all my projects?
If your project has the .svn directories (only the Eclipse integration 'has gone missing') you could try Team -> Share Project. In my workspace, Subclipse noticed the presence of the SVN folders and created the appropriate connection.
Edit: if you do not have the Share Project menu maybe the Eclipse installation 'got screwed'. If you do not have the Share Project menu in a newly created project and you do not see the SVN preferences under Preferences --> Team then you should re-install the Subclipse plugin.
If you do not have the Share Project menu only the projects you previously shared with SVN, than you should delete and recreate all your projects (in the delete do not delete the project contents and after the delete select File -> Import -> Existing projects into Workspace).
I also had the same problem and there is a simple fix:
Just rename your project ( right click on the project - Refactor - Rename) and it will re-link your project with svn. (Then you can rename it back).
For me the only thing that worked was:
Copy the entire project.
Eclipse ask to synchronize.
Delete old project.
Rename copied project.
After upgrading to the newest GWT/Google app engine I have problems opening my workspace in Eclipse. On startup, Eclipse hangs almost immediately and needs to be closed. This happens only in the workspace where I use GWT with app engine, and I weren't able to consistently reproduce it - sometimes it starts normally, and sometimes I need to kill the proces and restart it. There is nothing in Eclipse error log. Eclipse version is Galileo, running on Windows 7 RC.
Anyone else had similar problems? I googled but Google is not my friend today.
EDIT: Still happens after upgrading to GWT 2.0.1.
I got frustrated with not being able to open my workspace today, and finally solved this by importing projects into a new clean workspace.
Create new workspace and open it in Eclipse (to create .metadata folder).
Close Eclipse.
Manually copy all settings from old workspace (the most important settings are stored in the .metadata/.plugins/org.eclipse.core.runtime/.settings directory). Alternatively, you could use File / Export / General / Preferences in Eclipse, and then File / Import them, but I wasn't able to open workspace to do that.
Open the new workspace.
File / Import / General / Existing projects into workspace. Select root folder of your old workspace, and take care to check "Copy project into workspace".
Restart Eclipse and check that everything in the new workspace is working as it should.
Delete your old workspace.
EDIT: Another, and a bit better workaround which apparently works:
Close Eclipse.
Temporary move offending project somewhere out of the workspace.
Start Eclipse, wait for workspace to load (it should).
Close Eclipse again.
Move the project back to workspace.
I used "eclipse -refresh". Apparently it hangs on refresh something, the lower right corner tells you, what it's doing. For me it was refreshing the gwt runtime in a specific project, maybe trying to find an update or something. If you don't want to reimport your whole workspace, try -refresh or move this project temporarily out of the way.
I just deleted the state.dat file in the GWT project metadata, which seemed to remove the blocking and then triggered a recompilation.
<workspace>/.metadata/.plugins/org.eclipse.core.resources/.projects/<GWT project>/org.eclipse.jdt.core/state.dat
This probably won't serve as a general solution, but it worked for me and it's a lot quicker than having to copy whole projects. Maybe another file will have the same effect. I think the trick is just to "damage" the GWT project metadata enough to have it rebuilt.