I have a 2yo GWT project that's getting a little big for a single module, and we're bringing in a new project and we'd like to share some code.
Accordingly, I've split the project into a 'common' codebase and a project-specific codebase. That split isn't perfect yet, but I can't seem to get Eclipse to launch the project. If I launch the project through "mvn gwt:run", it launches successfully, but if I launch it through Eclipse (Run As > Web Application) the server part fails to start up when a filter can't find the SLF4J LoggerFactory. If I do some introspection on the classpath from the servlet, it seems like all of the JARs in the project aren't on the classpath -- only the classes and dependent projects are there. The launch configuration classpath seems ok, and the command-line startup seems to work. It doesn't seem to matter if I use m2e (with its Maven Dependencies container) or "mvn eclipse:eclipse", which adds the JARs to the project .classpath directly. I'm running low on ideas. So: 1. Anyone experience this or something like it and know what I should look for? 2. How does the server get its classpath -- from the launch configuration classpath or something different? 3. Is anyone using multiple eclipse projects with the Google Eclipse Plugin successfully? (from other threads, it sounded like there were people who had it working, but ...) Any other thoughts or suggestions welcome. -- 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/-/ty-qiodo-4wJ. 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.
