you could also use maven and set up parent poms with dependants as required,
On Aug 15, 2:07 pm, Mike <mreynolds0...@gmail.com> wrote: > Hi, we have an existing web application (JSF, Seam on JBoss) and are > reimplementing portions of it in GWT. These portions will be separate > GWT modules, each with their own entry point. The application is > currently a single Eclipse project with Maven handling dependency > management and the GWT compile (gwt-maven-plugin). We have a couple > GWT modules implemented so far and have had little trouble getting all > the different tools working together. > > Now, we are looking to set up another, no entry-point, module from > which all the other modules will inherit. This modules will hold > shared code and resources. Ideally, we would like this shared module > to be in the same project. So far, our attempts to set up such a > module have been fruitless. GWT compiles do not produce artifacts for > the shared module or any for modules that inherit from it. Also, dev > mode will not load the JS file for any module that inherits from the > shared module. It seems like the approach we are taking would be > relatively common, so I am assuming we have not set up the project > correctly. Does anyone have any insights or know of any resources > that would be helpful? Thanks. -- 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.
