Saturday, February 21, 2015

Re: super-source and eclipse

How should this work with a second project?

If I a super/ folder as source and have a gwt.xml in super/emul.gwt.xml with: 

<super-source path=""/>

Then this will not work. The super source must be in a subfolder.

Am Freitag, 5. Oktober 2012 16:47:33 UTC+2 schrieb Thomas Broyer:

On Friday, October 5, 2012 3:28:51 PM UTC+2, Abraham Lin wrote:
Add the root of your super-source folder as a source folder (right-click the folder, open the "Build Path" submenu, and click "Use as Source Folder"). Eclipse should automatically make the necessary modifications to the parent source folder, but you might want to check to make sure.

Don't do that: Eclipse will then compile you super-source and you then risk making your non-client code using those classes fail (unit-tests, server-side, etc.)

To only get rid of the warnings, right-click on the super-source "package" and chose Build Path → Exclude. Or move the super-source into a sibling folder hierarchy that you do not import as a Source Folder in Eclipse but only as a Folder (this is the approach taken by GWT itself: "src/" contains code to be compiled, "super/" contain super-source, e.g. src/com/google/gwt/core/client/impl/ vs. super/com/google/gwt/core/translatable/com/google/gwt/core/client/impl/ – a mix of both approaches actually, as newer modules such as use a "super" subfolder in the "src/" branch)
And if you want the "full power" of Eclipse for super-source classes, then create another Eclipse project where you import the super-source folder as a Source Folder (again, that's what GWT does: vs.

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment