> Neither one (depending on your build tool though). Sure, I get that Maven/Gradle/Ant will go through a copy-to-target step first, and so not use any src/... artifacts. So, for them, having the Jetty classloader not use the project classpath makes sense.
But at least we way run DevMode in Eclipse (as vanilla .launch files with DevMode as the main class), we pass -war src/main/webapp, so we can run directly against src/ without any copy-to-target/build system steps at all. And so then all of our IvyDE-managed jars and project .class files come from the regular Eclipse/system classpath that "Java Applications" get. > I don't have a strong opinion though; I'd be fine just using the > system classloader as the parent of the webapp classloader (the end > result would be the same as if you deployed all your code and > dependencies to Jetty's lib/ or lib/ext/ or Tomcat's shared/ ); Which is the behavior today, right? That is what I'd generally prefer, given it allows the previous "only use Eclipse" sort of setup. > I think newbies would need/prefer warnings. I'd be fine with a warning that could be disabled... :-) - 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.
