I encountered an issue using the Gradle Tomcat Plugin (https://github.com/bmuschko/gradle-tomcat-plugin/issues/8) that seems to be due to the plugin's classpath being different between (1) a Project{} block inside the root build.gradle and (2) a sub-project build.gradle file.
If I put my sub-project specific build configuration in the root build.gradle, the classpath when invoking the plugin is such that it can't find one of its own classes using Class.forName. If I put the very same configuration in a separate build.gradle file in the sub-project directory, it works. This is perplexing. Is this a bug or a poorly-understood (by me) feature? Thanks, Alan Krueger -- View this message in context: http://gradle.1045684.n5.nabble.com/Classpath-differences-in-sub-project-build-gradle-files-tp4426268p4426268.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
