I've been wrestling with exactly this same problem for PMD and Findbugs, and an additional constraint that I have is the need to ensure that I'm _not_ dependent upon mavenCentral, and that the plugin can cleanly disable the task if it cannot be provided with configuration information to find findbugs/pmd (it will not be available everywhere).
Getting this pattern "correct" will actually facilitate the use of external plugins that require dependencies that may or may not exist, and need to come from some configuration location that the plugin user might need to easily override. -Spencer --- On Sat, 2/5/11, TheKaptain <[email protected]> wrote: From: TheKaptain <[email protected]> Subject: [gradle-dev] Re: findbugs plugin - some open issues To: [email protected] Date: Saturday, February 5, 2011, 9:34 PM Johannes, I'm not sure it's the best way to do it, but I added a configuration used exclusively by an internal Ant Task inside of a plugin declaration. That way there's no need to configure the dependency in a build script using the plugin. Checkout the source code if you're interested. https://github.com/kellyrob99/gradle-jslint-plugin/blob/master/src/main/groovy/org/kar/jslint/gradle/plugin/JSLintPlugin.groovy -- View this message in context: http://gradle.1045684.n5.nabble.com/findbugs-plugin-some-open-issues-tp3370115p3372924.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
