On Jan 6, 4:15 pm, Chris Ramsdale <[email protected]> wrote: > You're not doing anything wrong, this should work in a more automated > fashion.
On the other hand, it shouldn't be included in the build path when you hit "compile" or "run web application" because you usually: - put tests in the same package as the class under test - you generally don't <inherit name="com.google.gwt.junit.JUnit" /> because it's done automatically when running the tests So having the tests including in the "compile" and "run" build path would lead to loads of warnings about GWTTestCase's source code not being available. Is there a way for an Eclipse plug-in to mark a folder as a "tests source" folder? (to distinguish it from a normal "source folder"; so it could be easy to remove such folders from build path during compile/ run while still making it possible to customize your project layout (vs. having "test" being hard-coded as an exclusion in compile/run)). For instance, we do have 2 such "test folders", one for "plain java" tests and the other for GWTTestCase tests. They're in the build path and we just don't use the plug-in builtin's "compile" and "run" facilities (well, we do use "run as web application" and "run as GWT JUnit" kind of launches but we tweaked the classpath to remove the offending folders)
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
