> 6. In eclipse we just start Debug as Web application. (with all > libraries manually copied into war/WEB-INF/lib)
This is our main problem, and I don't think it is related to only maven builds. Instead of using the project's class path including references to other projects and external jars like any other Eclipse runner would do, Google's plugin decides to skip all of this and insists on using the jars in WEB-INF/lib. Quite against what I expected tbh, and the run configurations don't hint that either. What would really help us is for the plugin to use the class path as it is defined for the project, and not use the jars in WEB-INF/libs at all. This way, you can break your project up in modules which themselves are eclipse projects, so that you don't have to do a complete jar build and copy the results to the WEB-INF/lib dir of the GWT project, but instead can just keep working. This would help us develop more efficiently, and it would also be more 'correct' in the sense that there is no difference between what the project uses to compile and run.
-- 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-tool...@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.
