Thanks for the feedback Thomas, I was actually following the gwt_with_maven docs at the google developers page (tough only creating one maven war project). So I think it should be quite easy to split it up. BTW. do these 3 (or 4 respectively) modules go into separate VCS repositories or do all go into one? I guess they could be checked into separate VCS repositories as the dependency is handled by maven anyways.
How do you do deployment? Do you have a dedicated jetty instance on the production server and package the war and deploy it? On Friday, May 11, 2012 9:48:07 AM UTC+2, Thomas Broyer wrote: > > > > On Friday, May 11, 2012 9:09:17 AM UTC+2, Ümit Seren wrote: >> >> I have a question to the people who are using multi-module maven >> projects instead of one (I am currently developing a >> Spring/GWT/RequestFactory project as one big maven projects). >> I do much of the debugging in eclipse by starting a WTP jetty instance >> and then starting the GWT development mode. By this I can debug both >> backend and frontend and whenever I change something in the client code it >> will work without me restarting development mode and when i change >> something on the backend WTP should re-publish it and it should also work >> fine (although some stuff doesn't). >> >> I am using eclipse m2eclipse for dependency management. ( I don't use mvn >> jetty:run or so but WTP) . >> Does the same workflow also work when I split up the one maven module >> into multiple? (shared, client, server) >> I guess it should as the m2 will probably make sure that everything is in >> the right place. >> But maybe somebody has already experience with debugging a multi maven >> module in eclipse and can give some feedback. >> > > We've been doing it for more than 1½ year now, it works really well. I'd > never used jetty:start or gwt:run before working on the > gwt-maven-archetypes. > We only used WTP for a few months, and then switched to launching Jetty > from a shell script, with a context dedicated to development where it reads > classes and resources from our different projects: 'touch' the context file > and Jetty redeploys the app in seconds. We had a few issues with WTP (not > redeploying some JARs/classes, etc.) > As for GWT DevMode, you have to add the source folders of your > dependencies (the 'shared' project, possibly others) to the classpath in > your Eclipse launcher. Depending on the configuration of your servlet > container / deployed app, you might have to use the 'server' project's > project.build.outputDirectory or WTP's temporary folder as the -war folder > for the DevMode. > Have a look at > https://developers.google.com/eclipse/docs/faq#gwt_with_maven > -- 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/-/qS9zYo98t0gJ. 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.
