On Monday, March 7, 2011 3:18:29 PM UTC+1, Tobias wrote: > > Thanks, that is exactly what I was looking for. But how do you set up your > build paths to use these?
You have to include your java sources in the classpath (just like with GWTTestCase, even though they're "pure Java" unit tests), because both use a "RealJavaResource" class to feed the real class' source to the TypeOracle rather than "mock" one (you'll note that it's duplicated, because it's a hack that the GWT team is trying to find a better replacement; in the form of a reflection-based, rather than source-based, TypeOracle I believe, which was the reason for changing the com.google.gwt.core.ext.typeinfo.* classes into interfaces in GWT 2.2). In your own project, it should be enough to add your "src" and "test" fodlers to the classpath, as gwt-dev and gwt-user both embed their sources in the JARs. -- 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.
