If you're working with eclipse it's easy: Click on the project -> build path -> configure build path. Click on Source Tab -> add Folder -> add your test folder.
Now all tests should work :) I don't remember how to do this in command line java, maybe look at man? On 7 jun, 07:01, Keith Whittingham <[email protected]> wrote: > Not an expert but here's a fast answer that I think is right. > > The fact that code finds itself somewhere under .../client means that > it will be X-compiled into JavaScript. If it's not there it won't. I > had to move classes there to solve the problem. > > The reason for this, I guess, is that you can't expect everything to > be compiled into JS (e.g. read characters from the keyboard wouldn't > work in a browser), not to mention the loading time for a page. > > What I do is to locate most of the meat of the application on the > server and use value objects across the wire to the client so that the > code under .../client *just* does presentation layer stuff. This > forces a nice separation of concerns but sadly doesn't leverage the > distributed nature of the application to leverage all those unoccupied > CPU's out there > > Keith > > On Jun 7, 2009, at 12:43 AM, samsus wrote: > > > Im trying to use classes from apackageinside /src but outside the / > > src/<project_name>/client folder. Until now i didnt had much sucess, i > > get the following error: "No source code is available for type > > test.Test; did you forget to inherit a required module?" --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
