Yep, same conclusion under maven project ... Being tired with this I'm finally using the noserver configuration (running tomcat/wtp) that works perfectly well.
On Thu, Dec 24, 2009 at 2:49 PM, fuzebest <[email protected]> wrote: > Same here with GWT 2.0 final. > > I think the problem is in the GWT provided Jetty classloader > (somewhere in com.google.gwt.dev.shell.jetty.JettyLauncher > $WebAppContextWithReload) which ignores project classpath and includes > only the war directory content. > But this is only a wild guess... > > -- > > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > -- A coward is incapable of exhibiting love; it is the prerogative of the brave. -- Mohandas Gandhi -- 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.
