Hi Thomas, > (or rather, it'll work "too well", and won't detect that "something is > missing in WEB-INF/lib".
I'm attempting to follow along, but classloader semantics are "fun", so apologies if I'm wrong somewhere... So, to clarify, if I have a dependency, say foo.jar, that isn't GWT, and isn't Jetty, but my server-side code uses it, with your proposal, would it now have to be in (say) src/main/webapp/WEB-INF/lib? Or could it still come from the Eclipse classpath like it does today? My two cents is that foo.jar being on the Eclipse classpath is just fine/what I generally prefer anyway, even if it "works too well", as it means I can skip the "make a war" or "put all jars into WEB-INF/lib" steps while just developing. That said, you are right that it could lead to false positives, but I would really hope that developers are not using "it works on my machine in dev mode against my exploded war" as their criteria for "will work in production". Perhaps that is too optimistic. - Stephen -- 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.
