|Re: what causes eclipse to check (or not check) xml files [message #1012343 is a reply to message #986668]
||Thu, 21 February 2013 11:36
| Jan de Ruiter
Registered: November 2012
I finally found the solution myself.|
I thought both projects were identical, but that was not exactly true.
In examining the .project files, I found that the project that showed the xml errors had
and the other project had not. After searching the internet for validationbuilder I found that this is indeed the xml checker.
Having it present in the .profile, forces all xml files to be validated after each build and/or change, causing a red cross on the faulty files.
In the other project, the same files had the same errors, and when 'validate' was done manually on such a file, the file would show the same error. But it would not automatically show after each build.
Removing this buildcommand from the .project, does not remove the red crosses, because they have already been detected. They can only be cleared by fixing the error and running validate manually.
An alternative is to remove from the workspace the file:
This will reset all red crosses, until the next explicit validation.
Powered by FUDForum
. Page generated in 0.87997 seconds