This should work as-is as long as the build for your plugin defines a compile
dependency on the FindbugsPlugin artifact.


--
Peter Niederwieser
Principal Engineer, Gradleware 
http://gradleware.com
Creator, Spock Framework 
http://spockframework.org
Twitter: @pniederw


lessonz wrote:
> 
> I've got a project that looks like this:
> 
> /**
> *******************************************************************************/
> buildscript {
>     repositories {
>         mavenRepo urls: "${repoBase}/${resolverRepoLocation}"
>         ivy {
>             name = 'snapshotRepository'
>             m2compatible = true
>             artifactPattern
> "${repoBase}/${snapshotPublishRepoLocation}/[organisation]/[module]/[revision]/[module]-[revision](-[classifier]).[ext]"
>         }
>     }
>     dependencies {
>               classpath 'lessonz:common-java:+'
>       }
> }
> /**
> *******************************************************************************/
> 
> apply plugin: 'common-java'
> 
> dependencies {
>     ...
> }
> 
> "common-java" is a plugin I'm trying to get working that I wrote. Mostly
> it sets properties for different tasks I want to be available across my
> different projects. It does have a few new tasks. The problem appears to
> be when I try to load in other third party plugins, like the ones listed
> here: http://wiki.gradle.org/display/GRADLE/Plugins When I get to:
> 
>     def void apply(Project project) {
>         ...
>         project.plugins.apply(FindbugsPlugin)
>         ...
>     }
> 
> 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?
> 
> Thanks.
> 


--
View this message in context: 
http://gradle.1045684.n5.nabble.com/Dependencies-of-a-plugin-tp4722054p4722079.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


Reply via email to