DevMode does support hot-deploy (you have to "trigger" it though, by clicking on the "reload web server" button –yellow spinning double-arrow in Eclipse's Development Mode view–), but it loads the server classes from the webapp's WEB-INF. Doing a "mvn package" will copy all dependencies to WEB-INF/lib and compile your classes to WEB-INF/classes so DevMode will be able to pick them up; but then if you change the server-side code, you have to make sure the WEB-INF is updated (for classes, you can tell Eclipse to compile to WEB-INF/classes, which should be the default with m2eclipse and m2e-wtp integration; but for dependencies, you have to run "mvn war:exploded" again –there might be another, faster, maven goal for that–). DevMode also loads the "web resources" from the webapp, so you have to ensure that changes to made to src/main/webapp are reflected in the webapp; again, "mvn war:exploded" to the rescue. With WTP and m2e-wtp integration, Eclipse WTP takes care of that "synchronization" for you, but then you don't use DevMode's embedded server.
-- 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.
