This seems to be the case for general gwt compilation and is not exclusive to gwt junit testing.
On Feb 22, 6:30 am, jopaki <[email protected]> wrote: > It seems when running GWTTestCase derived tests, module source path > declarations in inherited modules are not honored. Now my module > *.gwt.xml files are salted over an array of separate jars on the > classpath but all should be ok since gwt module resolution is based on > the "logical" path right? > > I'm running my gwt junit tests via maven 2.0.10 against GWT 1.6 > snapshot-2009.02.09 and have maven's surefire plugin to *not* use the > system classloader. My other non multi-module GWTTestCases ( i.e. no > "nested" module source path declarations - everything resides under > the default "client" package.) work fine. > > Anyone? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
