As a Mojo despot for a long time, you can count me as a binding vote :-) On Mon, Mar 30, 2009 at 12:55 AM, Garvin LeClaire <[email protected] > wrote:
> Hi, > The vote has passed with the following result : > > +1 (binding): Garvin, LeClaire > > +1 (non-binding): Arnaud Heritier, Pablo Saavedra > > +0 (binding): Benjamin Bentmannn > > > > I will promote the artifacts to the central repo. > > Regards, > > > > Garvin LeClaire > [email protected] > > > > > Garvin LeClaire wrote: > >> The Maven Findbugs team would like to release Maven Findbugs Plugin >> version 2.0 >> >> This plugin allows the developer to run Findbugs analysis against a Maven >> project and produce site output in HTML to match other site reports. There >> are option to produce other XML outputs which are used by other plugins. >> >> Issues fixed in this release: >> >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&fixfor=14335&pid=11701&status=6&sorter/field=issuekey&sorter/order=DESC&sorter/field=issuetype&sorter/order=DESC >> >> >> More information can be found at the plugin site: >> http://mojo.codehaus.org/findbugs-maven-plugin/ >> >> >> Issues Can be registered in JIRA at: >> http://jira.codehaus.org/browse/MFINDBUGS >> >> >> More information on FindBugs >> http://findbugs.sourceforge.net/index.html >> >> >> >> You can test the Maven Findbugs Plugin in your own project by adding the >> following dependency: >> >> <dependency> >> <groupId>org.codehaus.mojo</groupId> >> <artifactId>findbugs-maven-plugin</artifactId> >> <version>2.0-SNAPSHOT</version> >> </dependency> >> >> >> >> *NOTE* Version 2.0 and greater of the Maven Findbugs plugin will require >> Maven to be run with a minimum of Java 5. This is consistent with Findbugs >> requirement for their versions of 1.3.X and greater. >> >> >> >> >> Vote open for 72 hours. >> >> [ ] +1 >> [ ] +0 >> [ ] -1 >> >> -- >> >> Regards, >> >> >> >> Garvin LeClaire >> [email protected] >> >> -- Arnaud
