> trying to apply a third party plugin, it can't because the dependency isn't > present (in the example above the FindbugsPlugin). I think I could just add > it to buildscript's dependencies, but I was hoping to find a way to not have > to do that, that just having the dependency of "common-java" in there would > take care of it. Any ideas?
Currently, there is no way to configure the build script class path from anywhere but the build script itself. This means that you either have to roll all of your build scripts up into the top level one, or have the same build script configuration block in each sub projects build script. This is a known shortcoming and there has been some discussion on this list recently about making this easier to manage. Actually, it may be possible to do something with the buildSrc mechanism as a workaround as its output is implicitly placed on the classpath for all build scripts in the whole project. Write back if you are interested in trying this route. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
