Re: super-source and eclipse

On Friday, October 5, 2012 5:36:26 PM UTC+2, Abraham Lin wrote:

On Friday, October 5, 2012 10:47:33 AM UTC-4, Thomas Broyer wrote:

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.

It's not only about client vs. server, it also affects non-GWTTestCase unit tests of your client code.

 

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/browse/trunk/eclipse/user/.classpath vs. http://code.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?

The files will only be compiled into the other Eclipse project, whose output dir is different from the "main" project. That other Eclipse project is only used for editing (so you can take advantage of Eclipse's refactoring or "search references" features for instance), everything else (tests, etc.) still has to be done in the "main" project, where the files are treated as resources, not source files.

--
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/-/77xUkhsu-UEJ.
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.