Hi Chris, Right now, we use a heuristic to exclude test directories from your project's classpath on execution. If the folder containing your test source is named "test", then we will not add it to your project's runtime classpath.
We use this heuristic because the plugin currently has no understanding of GWT modules, so it cannot distinguish between test code and source code. In a future version of the plugin, we are going to bake in GWT module information, which will mean that this heuristic will become unnecessary. If it is not a reasonable solution to name the directory containing your test source code "test", another option is to edit the launch configuration for your application, and remove the test folder from the runtime classpath. Rajeev On Tue, Jun 23, 2009 at 10:33 AM, chris gwt <[email protected]> wrote: > > Hi everyone, I've run into a little issue when launching hosted mode > with an eclipse run configuration. > > I believe the issue is that all of the source directories for my > project are included when compiling for hosted mode.. including unit > test directories that I don't want to include. > > My personal style is to put my unit test classes in the same package > as the class being tested, but in a different source directory. The > result of this is that if source/a.b.c.d is included in my gwt > configuration, then test/a.b.c.d seems to be getting compiled as well. > > If I understand whats going on, I want a way to exclude particular > source directories from the build.. is that possible? > > Chris > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
