> > In the end, I wonder if we shouldn't just basically revert > https://code.google.com/p/google-web-toolkit/source/detail?r=4944, except > issuing a warning when we find the class in the system classpath (but > without automatically adding the JAR to the classpath and instead just > saying they should move it to WEB-INF/lib). Maybe we could add a switch (in > the form of a system property) to allow loading from the system classloader > (not restricted to Jetty system and server classes). > > What do you think? >
IMHO embedded jetty should behave like any other production server. If something is missing in WEB-INF/lib and is not provided by the server itself it should fail. And if people have production servers that provide additional API's (that shouldn't be in WEB-INF/lib) they should use -noserver instead. -- J. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
