Johannes Buehler-3 wrote: > > - I defined a findbugs configuration within the plugin in order be able > to pass the findbugs classpath to the findbugs ant task. This results in > the need to declare a findbugs configuration in the buildscript, which > is of course not a good thing. >
I guess the FindBugs plugin should work similar to the code quality plugin in that it adds a task per source set. See "Chapter 25. The Code Quality Plugin" in the user guide. SourceSet provides access to the classes directory and the compile class path. I think it's also important to have a way to run FindBugs for, say, Java but not Groovy code. It's easy to get just the Java sources with SourceSet.getAllJava(), but the question is how to map the sources to their corresponding classes. This seems to be difficult for source files that contain multiple classes or aren't named after the class. In languages like Groovy and Scala, this is a common situation. Johannes Buehler-3 wrote: > > - The findbugs task extends SourceTask, would the AbstractCompile be > more appropriate, cause findbugs uses the bytecode for the analysis. > I think neither is appropriate. FindBugs doesn't analyze the sources, and it doesn't compile anything either. ConventionTask seems like a good choice. -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradle Inc. http://www.gradle.biz Founder, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/findbugs-plugin-some-open-issues-tp3370115p3370219.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
