rationalblue wrote:Hence, I infer that the problem I identified is confined to the Eclipse/GWT Designer configuration. I am able to resume progress -- I can build a project with xml functionality, and edit/compile/deploy it with the GWT Designer functionality. But, the requirement to originate all projects that intend to use the xml (or similarly packaged gwt libraries) using the shell-script is cumbersome. If you can identify a configuration fix so that the GWT Designer New Java Project feature achieves the same result, it would be greatly appreciated.
com.google.gwt.xml.client.XMLParser can not be found in source packages. Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly
rationalblue wrote:However, as I said earlier -- I observed that the Eclipse editor continued to flag the import statements AFTER I had included the appropriate <inherits..> tag in the config xml file. It continued to flag the import statements, and new ones added, EVEN THOUGH it also displayed the correct and appropriate documentation in the code-completion popup as the lines were being entered. Moreover, the code compiled and deployed correctly without error, despite the red-underscored lines in the edit window.
rationalblue wrote:Just a few minutes ago, I determined that executing a "Clean" will apparently cause the editor to suddenly get smart and no longer flag the import statements. I have now tested that result a couple of times. I have no clue what "Clean" does, but I suspect that it clears some cache in the deep dark recesses of the editor; and that bowel movement causes it to recover its senses.
rationalblue wrote:As I said, I apologize if I've brought too much attention to this issue. And I do very much appreciate your support. The issue stumped me for a day and a half. The simple expedient of inserting the <inherits...> tag resolved the functional problem -- allowing the project to compile/deploy without errors. But it did NOT eliminate the troubling problem of confusion with the editor's unhappy name resolution problem.
rationalblue wrote:It now appears that the complete solution is simple:
<inherits...> in the appropriate project xml config file, AND
Clean before you Build.
rationalblue wrote:then it will flag the line with red underscore indicating it can't resolve the name.
rationalblue wrote:Edit the gwt.xml file to add the <inherits...> tag:
Save the gwt.xml file.
Return and note that the editor has still flagged the offending import statement with the red underscore and indicates it can't resolve the name.
rationalblue wrote:Save that java file. Saving does not change the editor's mood about the offending line.
rationalblue wrote:Attempt Build All, or Build Project.
rationalblue wrote:Do a Clean. You can now build and execute the project without problems.
rationalblue wrote:Your recommendation is definitely consistent with my observations -- the clue was the difference between Clean and Build All, which apparently doesn't really mean "build all,"....
Users browsing this forum: No registered users and 3 guests