Nowadays, many things in GWT require that it gets access to the compiled classes for your client code, so it's more a packaging issue (it's easier to package **/share/** in your WAR than to selectively pick only some classes from your **/client/** packages) than a compiling issue. AFAIK, the projectCreator predates the common usage of a "shared" package, that's probably the reason it still generates the RPC in **/client/**.
It should be a relatively easy patch, so if you want to contribute it, do not hesitate! On Thursday, March 22, 2012 9:46:59 PM UTC+1, Jamie wrote: > > Maybe this is the wrong board for this... but here goes. > > When I create a new project using the aw3s0m GWT Eclipse plugin, it > always creates the GWT RPC interfaces in the client package, instead > of the shared package. > So, that means I must compile the client package (or bits of it). > It seems to me that the shared package is the proper place for these > interfaces. > > So the first thing I always do is move the GWT RPC interfaces > (GreetingService and GreetingServiceAsync) to the shared package, and > then, later when I compile using an ant build file, I don't have to > compile the client package. > > Should I post this on the GWT developer forum? I didn't think this > quite fit the description. > I imagine it is really the projectCreator, and not necessarily the > Eclipse plugin. > > Thanks, > > Jamie. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/VLbzJ33yWl8J. 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.
