I didn't know about the eclipse plugin, i'll have to check that out when I have some time.
My classpath tab looks like: - Bootstrap Entries L JRE System Library - User Entries + MyProject (default classpath) L GWT \MyProject\source\ L Other \MyProject\source\ L classes \MyProject\web\WEB-INF\ L gwt-dev-windows.jar \MyProject\tools\GWT\lib\ The class that was giving me the error was in \MyProject\source \JUnitTests\(...)\a package included in the gwt config file\(...)\ I have since moved it to the default package in \MyProject\source \JunitTests\ and it has fixed the compile error.. but this seems the wrong way to fix it, and effects how i would design tests. On Jun 24, 1:20 pm, Rajeev Dayal <rda...@google.com> wrote: > Hey Chris, > I think I misunderstood you. I thought that you were using the Google Plugin > for Eclipse, but I guess that is not the case. If you're interested in using > it, you can find it here:http://code.google.com/eclipse > > Do you mind sending a screenshot of the classpath tab for the run > configuration that you're using? > > Rajeev > > On Wed, Jun 24, 2009 at 12:25 PM, chris <chris.rowland....@gmail.com> wrote: > > > Thanks for the reply.. I'm not sure what plugin you're referring to, > > though. > > > With regards to removing the test folder from the runtime classpath, > > it seems that the only option is to remove the entire project from the > > classpath.. I see no option to remove an individual source folder. > > > --Chris > > > On Jun 24, 11:04 am, Rajeev Dayal <rda...@google.com> wrote: > > > 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 <chris....@gmail.com> 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 Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
