I have a project I checked out with svn at work. It has the following associated with it in Package Explorer view of Eclipse:
project[trunk]
project-adhoctest[trunk/adhoctest]
project-jar[trunk/gazelle]
project-war[trunk/webapp]
Now I have a file in the project jar directory that I have put a breakpoint in. What is weird is that when debugger is launched, it always goes to the project[trunk]. This is really bad because I need to debug changes I make, not the trunk I checked out, but in project-jar.
The only other details is that I used maven to build dependencies when I imported this project. But, to make sure I did that right, I deleted everything and checked out this project again. Still same problem. I goggled quite a bit and asked others at work what could be going wrong, but haven't found a fix yet.
I use Eclipse Juno, 4.2.2
Thanks,
GeekyOmega
The problem is the build path was wrong, for me. It was looking at the entire workplace and choosing the trunk. When I re-installed eclipse, when I first ran debug, it asked me for the build path. I pointed the build path to the project folder project-jar instead. This fixed the issue for me.
You must go to run-->debug configuration and add the branch project in the Source tab
Using libgdx and just trying to get the HTML version of the basic setup is driving me crazy. I get this error
Loading modules
com.me.mygdxgame.GwtDefinition
[ERROR] Unable to find 'com/me/mygdxgame/GwtDefinition.gwt.xml' on your classpath; could be a typo, or maybe you forgot to include a classpath entry for source?
[ERROR] shell failed in doStartup method
this happens unless i actually named my app com.me.mygdxgame
i can't find any mention of this link(com.me.mygdxgame) any where in any of the .xml files and don't know where eclipse is getting it from. It gets that error on loading the index.html file but even in it the links are correct. Any help would be appreciated.
and i just searched for any mention of mygdxgame in all file in the workspace and got back 0
OK found out what it was.
The war directory was somehow getting cross linked to a same named game so no matter how many times i remade it it was getting linked to an old folder i had before. So even though all the directory's in the properties looked right the war folder was wrong. to fix it i had to un-check the "This project has a war folder" from the property's |Google|Web Application tab apply it then i tried running it as a web app it told me i didn't have a war directory so it would not run. That part may not be necessary but when i rechecked the box and re-selected the only war folder it would let me. the next time i ran i got to re-select the war folder from a full directory and not just my projects directory. This fixed the problem.
Just to clarify Eclipse seems to save war folder information by the name of the folder in which the project is contained what happened in my case was i had created a folder called MyGame in which i stored a project named com.me.mygdxgame the default for using libgdx. later i renamed that folder MyGame_old and started over with a new MyGame folder in which i named the project anything else doesn't matter the point is it never asked me for the war folder when i went to run it the first time, it just assumed somehow i was using the old one which was now in MyGame_old don't know how it found it but it did. so it was reading old files with bad links.
hopefully this might help someone else with this problem.
I came across this error as well but your suggested fix didn't work for me. After some investigating, here is what I did to get it to run: open the "Run Configurations" for the project and then click on the "Arguments" tab. Remove any reference to the com.me.mygdxgame.GwtDefintion in the arguments.
After this, project ran error free. Hope this helps.
After reading some posts it was clear that this problem was caused by GWT. One main reason for this problem is you are constantly reusing the same port and GWT is reusing the old properties.
There is really simple fix for this.
right click -html project.
Run-> run configuration.
Go to server tab.
check automatically select an unused port.
Press apply and
I'm using Eclipse Indigo on Mac 10.7.4. While working, I get these periodic, annoying dialogs
'Periodic workspace save.' has encountered a problem.
Could not write metadata for '/.org.eclipse.jdt.core.external.folders'.
/Users/davea/Dropbox/workspace/.metadata/.plugins/org.eclipse.core.resources/.projects/.org.eclipse.jdt.core.external.folders/.markers.snap (No such file or directory)
I seem to be able to continue as normal, but I was wondering how I can eliminate these errors.
I had the same problem.
'Periodic workspace save.' has encountered a problem.
Could not write metadata for '/External Files'. D:\java\fuentes\.metadata\.plugins\org.eclipse.core.resources\.projects\External
Files\.markers.snap (El sistema no puede hallar la ruta especificada)
I created the folder "External Files" and it worked fine. In a few minutes the files ".markers.snap" and ".syncinfo.snap" appeared in this folder and the message didn´t appear any more.
I fixed mine by closing eclipse and deleting the whole .metadata folder inside my workspace folder.
Today I faced the same issue consistently, whenever I exit the eclipse.
While trying the above solution provided by TS.xy, the below steps got rid of this issue for now.
Switch to new workspace and close the Eclipse.
Open the Eclipse with new workspace and after that switch to the actual workspace(in which
exception occurs).
Actual workspace loaded with all my previous projects.
Now exiting the Eclipse, does not result in that exception.
Hope that this step may work for someone.
Just for another data point, none of the above helped my situation. The way I finally got past this issue is that each time Eclipse complained about some folder not being there, I went on my hard drive and created the folder. E.g. after I see
Could not write metadata for '/servers'.
C:\...\.metadata\.plugins\org.eclipse.core.resources\.projects\servers\.markers.snap (The system cannot find the path specified.)
I create the "servers" folder (not the file inside it). This gets me to the next error. I went through 3-4 of these iterations (exiting Eclipse each time to force the save) before the issues went away.
HTH, Mark
This was simple for me -
Solution
(pre) the listed directory is not present, see pic
Run Eclipse, see the error shown in pic below. Close Eclipse
Create the directory (RemoteSystemsTempFiles) where it is looking
note: ignore the items in this folder (e.g. .markers), they are auto-generated
Restart Eclipse, problem solved!
Example Problem Message
Not sure why this took me so long to resolve, but quite easy now, and quite obvious in retrospect! ;)...
Using Ubuntu, got the same issue
I noticed that the owner of some of the directories in
~/workspace/.metadata/.plugins/ ...etc...
was root
changed owner to me and the error stopped happening.
Looks like the same sort of issue may be caused by multiple causes.
Close the Eclipse , Clear the .metadata folder completely.. Start Eclipse & Import the necessary project once again if your project references are deleted..
The solution that work for me is the following:
Delete .metadata folder
Restart eclipse
Solved it by setting workspace on a local folder, and set data from import project, from existing resources.
I encountered the same problem , my resolution was to rename the the folder name under the workspace folder. i.e. com.ibm.collaboration.realtime.alertmanager.embedded was renamed to com.ibm.collaboration.realtime.alertmanager.2embeddedxx and rebuilt my project.
In my case, because I've accidentally deleted my workspace folder, and I observed the 'Periodic workspace save has encountered a problem". To solve this issue, I just simply create a new workspace and load all my projects to the new one. Hope you can solve your problem by doing the same thing.
I also ran into this problem. My situation was a little different. I was using 'working sets' to group my projects inside of eclipse. What I had done was attempt to delete a project and received errors while deleting. Ignoring the errors I removed the project from my working set and thus didn't see that I even had the project anymore. When I received my error I didn't think to look through my package explorer with 'projects', opposed to working sets, as my top view. After switching to a top level view of projects I found the project that was half deleted and was able to delete its contents from both my workspace and the hard drive.
I haven't had the error since.
I had gotten a little too aggressive about removing some directories in my project area when I was running out of disk space, and deleted this directory. Eclipse can leave some huge core files if it crashes in your workspace directories, (I had 35 gig of them) so it's worth taking a look there in your workspaces occasionally.
Anyway, as per the problem I tried the 'create a directory' approach. And it worked.
I was also seeing this error when I closed Eclipse by the way, not only after the 'periodic save'. So the exit/restart was also part of this.
Note that the last item on the directory path specified in the error message is a file -- not a directory, so don't get confused here. Probably worth checking that the directory permissions are created correctly as well (as the other projects in the workspace I think).
Obviously this is a bug in the Eclipse code base, (creating the full directory path under the file that is being created), but had I not deleted it in the first place, I would not have caused it in the first place.
I have the same problem since yesterday. Yesterday, I fixed it by creating a new workspace and reimporting the projects. It seemed to work well, but today it started again.
So, today I created the folder and the file manually and gave the full permissions -rwxrwxrwx.
Seems to work again...
Close Eclipse. Open RemoteSystemsTempFiles folder in Workspace, and clear inside this folder. Again open eclipse and close, warn about .project. Press Ok, then open Eclipse.
Solved my problem that.
I ran into this problem today after they switched our anti-virus software to Kaspersky.
In my case, the platform is Windows 7. My workspace is stored on mapped network drive. The strange thing is that, even though this appears to be a permission issue, I could manipulate files and folders at the same level as the inaccessible file without incident. So far, the only two workarounds are to move the workspace to the local drive or to uninstall Kaspersky. Removing and re-installing Kaspersky without the firewall feature did not do the trick.
I will update this answer if and when we find a more accommodating solution, though I expect that will involve adjusting the anti-virus software, not Eclipse.
In my case, the drive I was storing my workspace on had become full downloading SDK updates full and I just needed to clear some space on it.
This happened to me because i deleted one of the resources files inside the .metadata folder in my workspace.
After trying all methods, deleting the .metadata folder in my workspace worked.
Infact, this nuke option seems to work when there are a lot of issues related to eclipse bugs. One such example is working-sets. Working-sets are extremely buggy(but useful) and it is there that most of my eclipse problems start.
Hope this helps someone.
I solved the problem switching the workspace.
Go to File (Switch workspace)
Select the destination and create a folder named Workspace
Run a Hello World and close Eclipse (notice that Eclipse creates the folder RemoteSystemsTempFiles automatically)
now copy all your projects into the new folder Workspace
Open Eclipse and if necessary (sometimes Eclipse does not show the projects) import all of them (go to File/ Open projects from File System)
After you exit the eclipse, there would be an specific failed reason.
Mine is that the DISK IS FULL so the eclipse can't write into it anymore.
Agree with #J-Dizzle,
I am a beginner in web-development and had a hard time solving this today.
Had similar problems when I was creating a SpringBoot project in STS.
Tried most of the solutions mentioned but they didn't work.
Tried removing .metadata folder and re-building my springboot project but still nothing worked.
NOTE : I had multiple workspace in STS and this error occurred after migrating a project from one workspace to another.
Solution : All you need to do is restart your eclipse/STS IDE and it will work just fine.
I'm working on an Android project in eclipse, and whenever I try to move or rename a source file, eclipse says it caught an exception while trying to refactor, that the file doesn't exist, and lets me either undo, or abort. I suspect it has something to do with mercurial because it's happened before, but besides that, I have no idea what is wrong. Anyone know how to fix this? I've already tried refreshing the entire project, cleaning the project, and closing and reopening the project, but I still can't even move a source file from one project to another.
UPDATE:
I've resorted to using the command prompt to manually move and rename my files. It wasn't that hard, but Eclipse is still not doing what it's supposed to do. I want to know how to fix this.
Its possibly related to this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=339866
I found updating both eclipse and hg fixed the error.
Right click on your project and click refresh. This is usually due to files being out of sync with the file system.
when I try to build my Eclipse project, I get the following error message:
The type org.eclipse.swt.widgets.Composite cannot be resolved. It is indirectly referenced from required .class files
Can anybody help me to solve this problem? The Java-Build-Path contains the Plug-in-Dependencies-Library and org.eclipse.swt... is listed there.
I didn't have the problem last week (though nothing should have changed in the meantime).
But it's not the first time that I get this typ of error...
Finally, I could solve the problem with creating a new workspace and importing my project.
I sometimes encounter this kind of stranges error and the only solutions I found to solve it are the following ones (no specific order and sometimes one is enough sometimes not):
Select the project and clean ONLY this project, then rebuild
Clean all the workspace
Restart the workbench
Disable "automatic build", clean all, the build only your project
Remove the project from the workspace WITHOUT removing it from Hard drive and then import it again
I think this is a PDE issue.
Hope this can help,
Manu