Benjamin Muschko wrote: > > The code doesn't actually use Class.forName(). It uses > Thread.currentThread().contextClassLoader.loadClass(). See this > https://github.com/bmuschko/gradle-tomcat-plugin/blob/master/embedded/src/main/groovy/org/gradle/api/plugins/tomcat/embedded/TomcatServerFactory.groovy > class for more information. >
I've looked at the source code of TomcatServerFactory. Why does it use the thread context class loader? How is it supposed to solve class loading conflicts as mentioned in the Javadoc? -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Blog: http://pniederw.wordpress.com Twitter: @pniederw -- View this message in context: http://gradle.1045684.n5.nabble.com/Classpath-differences-in-sub-project-build-gradle-files-tp4426268p4439988.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
