On Wednesday, September 12, 2012 4:46:57 PM UTC+2, tanteanni wrote: > > How does the issue you mentioned explains why all is running fine > (gwt:run, deployed) but it fails in eclipse hosted mode? Or how to get know > the name of the conflicting jar to be excluded via " > runClasspathExcludes"? > is gwt-maven-plugin 2.5-rc1 working with gwt 2.4? > > because my "only" problem is eclipse' hosted mode i want to be sure that > refactoring to multi modules is the only but sure way to solve this problem. >
Ah sorry, didn't see that gwt:run works OK. runClasspathExcludes won't change anything then, as it only applies to gwt:run. If your only problem is with Eclipse, then I don't see any other thing to do than compare the classpaths (run "mvn -X gwt:run", it should then display the classpath used for launching the DevMode; and compare to what's being used in the Eclipse launcher; there should be a mean –some process explorer, or maybe JConsole– to see what command line has been used by Eclipse to launch the DevMode and see what it put in the classpath) Also maybe try connecting to the DevMode even if nothing appears in Eclipse. As a last resort, create a "Java Application" run configuration in Eclipse, choosing com.google.gwt.dev.DevMode as the main class; that way you'll have complete control over what happens, and you can use "Debug as..." in Eclipse (much better than gwt:debug) -- 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/-/6Rt4DmJT9bsJ. 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.
