Now that we have the data available I think everyone should be a little proactive and
create
a jira subtask for investigating and potentially fixing a part of those warnings.
i.e. don't wait to be told; create a subtask and qualify/fix warnings in the area you
are
involved.
A lot of them might not make sense but I'm sure there are real gems hidden in there.
Thanks
/Dimitris
Shelly McGowan wrote:
I've published the FindBugs report set up by the JBoss QA team run against JBoss AS.
The reports can be viewed here:
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-findbug...
This report shows a total of 5675 warnings, 877 of which are categorized as High
Priority.
The report for Branch_5_x can be viewed here:
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-5.x-findbugs/...
The Branch_5_x report has 6089 warnings, 977 High Priority.
These issues should be addressed when committing to trunk or Branch_5_x. Take time out
to
look at the report data. Most of the warnings can be easily addressed.
I've started a parent JIRA task for tracking:
https://jira.jboss.org/jira/browse/JBAS-7295
and will create subtasks as needed after additional review of the report data.
Shelly
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development