Almost ready for FindBugs 1.3.9-rc1, need some pre-rc1 testers

[Bill Pugh]

I've been making a lot of changes to FindBugs:
   * clearing up old filed bugs
   * making the analysis results match the @NoWarning and  
@ExpectedWarning results
   * checking the results against the results from 1.3.8 and making  
sure the changes are good
   * Doing refactoring to separate out the GUI and cloud code, so that  
the core code doesn't depend
     upon them

I think I'm done with all the changes I expect to make, and ready to  
start moving to wider testing by more people.

I made enough changes over the past few days, and I don't have my  
usual suite of hardware and software to test FindBugs on, so I'd  
appreciate it if some of the more hard core members of the FindBugs  
community could do some sanity checking on the current HEAD version  
before I actually package up a release candidate. I don't want a lot  
of people testing out a release candidate if I made some stupid mistake.

Bill
_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@...
https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss

[Garvin LeClaire-2]

Bill,

This does not seem to be a new bug, but one I ran across refactoring the
Findbugs Maven2 plugin.   The xml files does not have a total for the
bug_count when using the visitor option.  The individual classes total
up, while the bug_count is Zero.


  <FindBugsSummary timestamp="Tue, 4 Aug 2009 22:47:10 -0400"
total_classes="0" referenced_classes="62" total_bugs="0" total_size="0"
num_packages="0" vm_version="1.5.0_19-137" cpu_seconds="1.64"
clock_seconds="1.66" peak_mbytes="32.87" alloc_mbytes="63.56"
gc_seconds="0.32">
    <FileStats path="UselessAssignments.java" bugCount="5" size="0"
bugHash="64b3431f3e95a2fa74153c93704ef18b"/>
    <FileStats path="UserMistakes.java" bugCount="1" size="0"
bugHash="c0896340ef24a6bc5b0d80148f50d53d"/>
...
  </FindBugsSummary>


Regards,



Garvin LeClaire
garvin.leclaire@...




Bill Pugh wrote:

> I've been making a lot of changes to FindBugs:
>    * clearing up old filed bugs
>    * making the analysis results match the @NoWarning and  
> @ExpectedWarning results
>    * checking the results against the results from 1.3.8 and making  
> sure the changes are good
>    * Doing refactoring to separate out the GUI and cloud code, so that  
> the core code doesn't depend
>      upon them
>
> I think I'm done with all the changes I expect to make, and ready to  
> start moving to wider testing by more people.
>
> I made enough changes over the past few days, and I don't have my  
> usual suite of hardware and software to test FindBugs on, so I'd  
> appreciate it if some of the more hard core members of the FindBugs  
> community could do some sanity checking on the current HEAD version  
> before I actually package up a release candidate. I don't want a lot  
> of people testing out a release candidate if I made some stupid mistake.
>
> Bill
> _______________________________________________
> Findbugs-discuss mailing list
> Findbugs-discuss@...
> https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
>
>  

_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@...
https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss

[Garvin LeClaire-2]

I have put the 1.3.9-rc1 version in our Maven test repository.
The URL is http://findbugs.googlecode.com/svn/repos/rc-repository/


I have released a 2.2-SNAPSHOT version of the Findbugs Maven plugin.  I
have done refactoring to reduce the dependency count.


Regards,



Garvin LeClaire
garvin.leclaire@...




Bill Pugh wrote:

> I've been making a lot of changes to FindBugs:
>    * clearing up old filed bugs
>    * making the analysis results match the @NoWarning and  
> @ExpectedWarning results
>    * checking the results against the results from 1.3.8 and making  
> sure the changes are good
>    * Doing refactoring to separate out the GUI and cloud code, so that  
> the core code doesn't depend
>      upon them
>
> I think I'm done with all the changes I expect to make, and ready to  
> start moving to wider testing by more people.
>
> I made enough changes over the past few days, and I don't have my  
> usual suite of hardware and software to test FindBugs on, so I'd  
> appreciate it if some of the more hard core members of the FindBugs  
> community could do some sanity checking on the current HEAD version  
> before I actually package up a release candidate. I don't want a lot  
> of people testing out a release candidate if I made some stupid mistake.
>
> Bill
> _______________________________________________
> Findbugs-discuss mailing list
> Findbugs-discuss@...
> https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
>
>  

_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@...
https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss