> > However, now that the error disappeared, I'll come back to the original >> question and see how it speeds up the development process. >> > > Now that you can have "resolve dependencies from the workspace" enabled in > Eclipse, the GWT Eclipse Plugin should automatically configure the launch > configuration to use the Eclipse project for the library and its source > folders; that means you don't need to "mvn install" and restart the dev > mode. So, problem solved? >
Looks good! It's also fine that I don't need to explicitely include the library source code in the jar anymore. However, when debugging and seeing a problem in server-side library code, I still have to stop the debugger, fix the problem and restart the debugging session. Can this also be improved? (There is a button "reload web server" in eclipse). > (and with a reactor build, using and configuring > net.ltgt.gwt.maven:gwt-maven-plugin:devmode in the root project, you get a > similar behavior, from the command line) > This reactor stuff sounds interesting to me. I think I'll move my projects to the modular-webapp archetype, allthough I'm not happy with the fact that the three subprojects must be unique at the top-level. And they also have a different package structure. The projects created with webAppCreator have "client", "server" and "shared" in their package names, while modular-webapp doesn't. Since eclipse refactoring doesn't work on whole directory trees, this will be a lot of manual work... Thanks Magnus -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
