- This topic has 3 replies, 3 voices, and was last updated 13 years ago by
.
-
Posts
-
I recently upgraded to 10.0 and now have major JavaScript validation issues. I am working on a large project that contains over 1000 jsp files and almost all of them include statements like: onkeypress=”return textAreaLimit(this, 255)”. That should be perfectly valid and validated fine in 9.1. It causes several thousand validation errors in my project.
If that wasn’t a serious enough issue I am having a problem where MyEclipse occasionally ignores the setting to exclude resources after my project is refreshed, either manually or when I relaunch MyEclipse. I go to my project properties, then MyEclipse->Validation->Excluded Resources and then check my folders that contain my jsps to hide the validation errors. Then sometimes MyEclipse seems to ignore that setting and all of my jsp validation errors return. The only way to fix it is to go back into the excluded resources section, uncheck the resources, wait for the long process to re-validate, and then recheck the resources and then again wait for it to re-validate.
I found references to the eclipse bug online associated with my validation issues here: https://bugs.eclipse.org/bugs/show_bug.cgi?format=multiple&id=353198
gmascherino
1) A workaround for now, please go to Window > Preferences > MyEclipse > Files & Editors > Javascript > Validator > Errors & Warnings – disable the semantic validation here and your error should disappear.
We are going to fix this particular problem for 10.0.1, so that you don’t see it even when the semantic validation is enabled.
2) instead of Excluding validation using those settings, you can go to the global validation preferences at Window > Preferences > MyEclipse > Validation and turn off the JS validators there, or you could do that at the project level too.
A fix for this issue has been released in our milestone stream release of 10.0.1; please see this link for further details.
