On 09/03/2010 04:53 PM, Antoine Toulme wrote:
I think what would be critical is that we set up
something so that it's easy for projects to get a FindBugs report.
OK to discuss it at the next meeting.
Oh you mean something like:
http://dev.eclipse.org/viewcvs/index.cgi/sourceediting/development/athena/org.eclipse.wst.xml.xpath2.releng/buildUtils.xml?view=markup&root=WebTools_Project
It includes two targets:
findbugs and dry
Executing either the target will also automatically have it download
the needed findbugs jar files and setup the ant task. The only
thing that has to be changed is where to find the source files.
They could also use the FindBugs plugin and run against their
workspace.
Ideally they add it as part of their automated build and publish the
results using Hudson.
Dave
On Fri, Sep 3, 2010 at 11:44, David
Carver <d_a_carver@xxxxxxxxx>
wrote:
I sent this to Wayne and Lynne. They
suggested I bring it before the architecture council for
discussion:
Here is something that I think would be an interesting
endevor to
undertake and I don't think Apache or any other open source
foundation
has done this.
In 2009, Google held a day or two for a FindBugs FixIt.
http://findbugs.sourceforge.net/
http://www.nytimes.com/2007/10/21/jobs/21pre.html
Basically, the engineers devoted two days to fixing bugs
that FindBugs
reported. It is no secrete if your run these Static Code
Analysis
tools that some of the core systems we have and use at
eclipse are not
as clean as they could be.
So, what I'm proposing is that there be a little contest
amongst the
various eclipse projects. Those that want to participate
can run
FindBugs against their code base, and publish the initial
baseline
results. They then can devote one milestone in which
they report
the difference between what Findbugs found to begin with
and what the
end of that Milestone reports. The one with the most
improvement
could get some sort of Recognition or Badge or something.
Maybe
bragging rights that they have the cleanest code.
The ultimate goal though is to improve the code base for
the
adopters. The more bugs we eliminate up front instead of
waiting for
them to be reported the better for the adopters and
community. This
is just one way we could do it, and make it a little
competition.
Thoughts?
I can open a bug for this as well, if necessary.
Dave
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes
internal to the Eclipse Foundation. To be permanently
removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
|
