logo       

Mining bugs: msg#00043

java.findbugs.general

Subject: Mining bugs

Hi,

Lately I've been playing with bug mining features. I have a few comments ;)

First, I'm facing one issue: if you run the analysis on xml files generated
with messages (xml:withMessages flag from ant task), then the messages are
lost (filtered out by 'edu.umd.cs.findbugs.workflow.SetBugDatabaseInfo',
probably also by 'edu.umd.cs.findbugs.workflow.Update')

Then I ended by putting together a few improvments that will allow to have
this analysis easier and nicer to use:

1- keep messages!

2- in output generated by edu.umd.cs.findbugs.workflow.Update, instead (or
in addition) of having attributes introducedByChange="true" and
removedByChange="true", having attributes that gives the version bug
instances where introduced/removed.

3- be able to store analysis from
'edu.umd.cs.findbugs.workflow.MineBugHistory' within the xml file as
subtags/attributes of <AppVersion .../> tags.

4- having these features available from the main ant task or new ant tasks.

When/if these improvments are implemented in a future release, I'll be
willing to work on fancy.xsl in order to add new capabilities to html output
(i'm mainly thinking on adding an history page and filtering bugs by version
capability on other pages).

Let me know if you want me to enter this in the tracker.
BTW, should we use sf or google tracker?


Thanks for your work,
Regards,

Etienne



<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise