I’ll throw in that we have about 15 licenses of MyEclipse, across mutliple OSes (primarily OS X 10.6 and Win XP), and have similar problems with XML (struts.xml), JSP, JS, etc across most machines (on Eclipse 3.5.x w/ ME 8 and Eclipse 3.6.x and ME 9).
I skimmed through the comments above, so sorry if its being addressed or I missed something.
Why is it necessary to explicitly remove problem files in project specific settings? Shouldn’t disabling validation at the workspace level turn it off? I just created a new workspace, imported some existing projects, and almost every web project was giving build errors on struts.xml (for Struts 2), AFTER I had disabled it from Eclipse’s preferences (Uncheck All). Going file-by-file and excluding seems to work, but why is that even necessary? Can we provide a workspace level validation-ignore file list?
I’m on OS X 10.6.7, Eclipse 3.6.2 Classic Cocoa 32-bit, and MyEclipse 9.0.0.
Brian