Hmm, that's a good idea. I was thinking it'd probably make the code cleaner too. Just put all the GWT specific stuff in the same top level package and other client side classes like controllers, etc in another top level package. Thanks!
-- Arthur Kalmenson On Mon, Feb 2, 2009 at 12:31 AM, <[email protected]> wrote: > > Just create a separate module for GWT stuff. There shouldn't be > anything in that except GWT-specific stuff, and therefore, > GWT-specific test cases. If for some strange reason you're not able to > do this, then create a GWT-specific test module which does nothing but > test your GWT components. > > -jesse > > On Sun, Feb 1, 2009 at 3:21 PM, Arthur Kalmenson <[email protected]> > wrote: > > > > In the past, when I was using Ant, I would have gwttest directory for > > GWTTestCase tests, and a test directory for regular tests. While the > > package structures were the same in both folders, I'd wouldn't add the > > test directory to the classpath when running GWTTestCases. Is there a > > similar approach I can take with gwt-maven? Thank you. > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" 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/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
