On 26 July 2011 16:11, Steve Wedig <[email protected]> wrote: > Hello, > > I've only used Java for GWT purposes, so sorry in advance if this is a > dumb question :) > > In Eclipse, I would like to have my GWT project depend on code in a > non-GWT project (so I don't think GWT module inheritance will work). > > In setting this up, my preferences in order would be: > 1. No need to compile the parent project into a JAR, for both dev-mode > and deployment compilation. > 2. Need to compile into JAR when deploying, but not for dev-mode. > 3. Need to compile into JAR even during development (which would be > pretty painful). > > I'm wondering, how can I set up any of these?
The GWT compiler simply needs the source of your dependency available at compile time. It doesn't matter whether it's in the form of a JAR file or a directory on the classpath. You do need to make sure GWT knows where to look, so see <source path="..."> (for your *.gwt.xml). Be careful that your new dependency doesn't use reflection because most of that is not supported by GWT (for obvious reasons). -- 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.
