I am migrating a projet from GWT 1.5 to 1.6. The server-side of my project uses my project classes and a number of external jars (that are located for example in my maven local repository).
With GWT 1.5, having these jars in the classpath defined in the launcher was enough to have the embedded Tomcat pick them up. With GWT 1.6, it seems that the embedded Jetty ignores them (and thus I have class no found exceptions server side). I could make it work by copying the jars in the war/WEB-INF/lib folder, but this really does not fit in our dev process. Is there any way I could force Jetty to behave like Tomcat before and "see" my external jars where they are (or am I doiong something wrong)?. Thanks --~--~---------~--~----~------------~-------~--~----~ 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-Toolkit@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 -~----------~----~----~----~------~----~------~--~---
