On 03/04/2009 02:53 PM, Markus Knittig wrote: > Currently it seems that Jetty only loads class files and jars from > WEB-INF/classes and WEB-INF/lib. The classpath argument are getting > ignored (worked with Tomcat). I tried to add extra classpath folder via > jetty-web.xml / jetty-env.xml, but that doesn't seems to work (e.g. > Spring throws an ClassNotFoundException before the extra classpath is > added). > This seems like a step backward to me. Especially since I use Maven and > Jetty would not only be flexible enough to load classes / jars from > different locations, but can also load static webapp files from differnt > location: > http://docs.codehaus.org/display/JETTY/Multiple+WebApp+Source+Directory > This would make things with Maven much cleaner / easier...
Seems like an known issue: http://code.google.com/p/google-web-toolkit/issues/detail?id=3435 Best regards, Markus --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
