Comments on: Summary of Some of the Pecularities Involving GWT Eclipse Tooling and Super-Source http://blog.echo-flow.com/2009/05/19/summary-of-some-of-the-pecularities-involving-gwt-eclipse-tooling-and-super-source/ MODELLING AND SIMULATION, WEB ENGINEERING, USER INTERFACES Wed, 10 Aug 2011 20:54:30 +0000 http://wordpress.org/?v=2.9 hourly 1 By: admin http://blog.echo-flow.com/2009/05/19/summary-of-some-of-the-pecularities-involving-gwt-eclipse-tooling-and-super-source/comment-page-1/#comment-167 admin Wed, 10 Aug 2011 20:54:30 +0000 http://blog.echo-flow.com/?p=14#comment-167 Sorry Tyler, I never did sort this out. Sorry Tyler, I never did sort this out.

]]> By: Tyler Van Gorder http://blog.echo-flow.com/2009/05/19/summary-of-some-of-the-pecularities-involving-gwt-eclipse-tooling-and-super-source/comment-page-1/#comment-166 Tyler Van Gorder Wed, 10 Aug 2011 19:51:47 +0000 http://blog.echo-flow.com/?p=14#comment-166 Did you ever find a solution to the mismatch between the eclipse gwt tooling and the use of super-source? I ran into the same problem. I am wondering if you tell eclipse to exclude the "hack" package, if that will work correctly? By "exclude" I mean going to the project's Java Build Path, on the "Source" tab selecting the source folder and adding an "Exclude Rule" Thanks Did you ever find a solution to the mismatch between the eclipse gwt tooling and the use of super-source? I ran into the same problem. I am wondering if you tell eclipse to exclude the “hack” package, if that will work correctly? By “exclude” I mean going to the project’s Java Build Path, on the “Source” tab selecting the source folder and adding an “Exclude Rule”

Thanks

]]>