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.)
Ah, that's true. I'm used to separating client and server code into separate projects, so this hadn't occurred to me.
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: http://code.google.com/p/google-web-toolkit/source/ vs. http://code.browse/trunk/eclipse/user/. classpath google.com/p/google-web- )toolkit/source/browse/trunk/ eclipse/lang/.classpath
Doesn't this lead to the same problem as adding the super-source folder directly as a source folder? If the fundamental problem is that client-side tests and server-side tests need different classpath configurations, then you would presumably need separate projects or separate testing configurations (with includes/excludes as appropriate).
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/SuC37bV3K5wJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment