[QAS]

– System Setup ——————————-
Operating System and version:
Eclipse version: 3.8.4
Eclipse build id: M7
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: VSS
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 4
MyEclipse version: 3.8.4 M7
Eclipse JDK version: 5.0 03
Application Server JDK version: 5.0 03
Are there any exceptions in the Eclipse log file? No.
– Message Body ——————————-

Hi,

I am building a project which is connected to VSS to our Tomcat installation using deploy. It’s all fine but I found that some xml config files that we keep in the classes folder so that they can be picked up by Tomcat get removed by Eclipse when building sometimes. That’s easy enough to sort out, we just use Navigator to go to classes and get Latest Version to bring the files down again.

My issue is that Eclipse is stuck with the following error on one such file after a rebuild. The file did indeed go missing on the rebuild as Eclipse clears its personal bin/classes folder out where this file was expected. But I have since grabbed this file, it is definately there 100%, I have rebuilt the whole project, refreshed the whole project and done literally everything I can think of to make Eclipse aware that this file is back where it wants it.

Yet nothing will shift this now invalid error message. I have seen this since Eclipse M4 by the way and sometimes i’ve made it go away but more by luck or restarting the whole project.

2 File not found: “C:\webapps-dev\iq\WebRoot\WEB-INF\classes\hibernate.cfg.xml (The system cannot find the file specified)”. iq line 1 18 May 2005 12:50:47

Your help appreciated if available.
Allistair.

[Scott Anderson]

Allistair,

It’s all fine but I found that some xml config files that we keep in the classes folder so that they can be picked up by Tomcat get removed by Eclipse when building sometimes. That’s easy enough to sort out, we just use Navigator to go to classes and get Latest Version to bring the files down again.

When Eclipse builds your Java classes, it deletes everything in the output directory before the build starts. That’s why your xml files are going away. The proper way to address this is to check the XML files into the locations they’re needed in your Java source folder. When the Eclipse builder finds non-Java files in the source tree, it “builds” them by simply copying them to the same relative location in the build output folder. Moving your files as suggested, into the source tree, will remove this little annoyance for you, once and for all and should address your “missing file” issue as well.

[QAS]

Hi,

You’re absolutely right, my mistake. I’ve since moved all these files to SRC and they get deployed to classes. Perfect.

Except the file not found messages never go away. They are persistent and annoying!

I have tried creating a local dummy copy of the file where it thinks they should be and then using Delete to remove from within Eclipse to force it to recognise they are gone but something somewhere is locking this error into place. I honestly don’t think Eclipse is all right here.

[Scott Anderson]

On the folder that is reporting the error, right click on it in the Package Explorer View and select MyEclipse > Remove All Problem Markers. That should do the trick.

[QAS]

Thanks for the suggestion, I will remember it. I decided that I would quickly rebuild the project, only took a minute, but I wanted to raise it as a potential problem in Eclipse .. it just seems odd that on a manual build, manual local refresh and so on, that it would not say .. ok I have 2 errors which relate to a file not being present, are they there now or not. (since i copied dummy ones into the locations). Or perhaps saying to me … you know what, these files I can’t find anymore, so is it ok to remove them?

I appreciate this is not a MyEclipse issue, so no need to reply to my mini-rant :)))

Thanks guys, Allistair.

[Paul Stanton]

i get that error for every xml file i delete. the problem marker is on the project in package explorer. why isn’t the delete clean? myeclipse bug?

[Paul Stanton]

MyEclipse>Remove Validation Markers seems to do the trick btw

[Scott Anderson]

Markers should be removed upon deletion and I’ll log that. You’ve found the correct workaround, however.

[Author]

Posts