Description of problem: After importing Helloworld Errai quickstart, the javascript validation error occurs. Version-Release number of selected component (if applicable): WFK2 ER8 EAP6 CR1 JBDS5 CR1 How reproducible: Always. Steps to Reproduce: 1. import jboss-as-quickstart-helloworld-errai into JBDS Actual results: Javascript validation error occurs. Expected results: No errors should be shown after import. Additional info: The workaround is to exclude specific JS files (5.cache.js) from being validated.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: JBoss Developer Studio complains about JavaScript files distributed with the example being invalid. This does not impair functionality of the example. To get rid of the error, exclude specific JS files (5.cache.js) from being validated.
I'd recommend disabling JavaScript validation on everything under src/main/webapp/${moduleName}/**. Rationale: 1. The warnings that we get from JavaScript validation are pointing out potential programming problems (that is, the JavaScript code may not be doing what the author intended). Although this is really useful for handwritten code, these warnings are always false positives with code generated by GWT. The code does exactly what the GWT compiler intended. 2. JavaScript validation takes time to complete, so even if people learn to ignore the warnings, their IDE will be hammering the CPU needlessly.
Thanks, Jonathan! Karel or Tomas, we need to change a little Release notes text to say to exclude that directory from JS validations
Marek, can't we rather ship JBDS configuration disabling the JS validation with the example out of the box?
agree that we should provide everything what user/customer can find easy to use, but I have some concerns with mixing really wanted eclipse settings and by mistake added other settings from local developments.
Has been moved 2 releases, now to WFK 2.2. Is a "known issue" with a simple workaround with JBDS. Decide before WFK 2.2 whether is "wont fix" or if we can address in WFK...
I can not reproduce this issue anymore: (this is related to bug 874090 - Stefan already verified) Testing with: WFK-2.2.0.ER1 EAP-6.0.1.GA JBDS: Version: 6.0.0.GA Build id: GA-v20121206-1855-B186 Build date: 20121206-1855 Please confirm this issue is gone
True, using exactly the same versions as Pavel gives no errors after importing. Changing status to verified.
Closed as CURRENTRELEASE, part of WFK 2.2.0 distributables.