Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse.org-architecture-council] [Bug 326807] New: FindBugs FixIt Challenge

https://bugs.eclipse.org/bugs/show_bug.cgi?id=326807 
Product/Component: Community / Architecture Council

           Summary: FindBugs FixIt Challenge
    Classification: Eclipse Foundation
           Product: Community
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Architecture Council
        AssignedTo: eclipse.org-architecture-council@xxxxxxxxxxx
        ReportedBy: d_a_carver@xxxxxxxxx


Taking a queue from the FindBugs FixIt challenge that Google went through, I
think it would be a good if one milestone was devoted on a volunteer basis for
Eclipse.org projects to see how many bugs they can fix.   The goal is to
provide further stability for adopters, the more bugs we fix now, the less we
have to deal with later.

In order to make this easy to run, and integrate with a build, I have created
an Ant Build script that will do most of the heavy lifting for you.   It will
automatically download the findbugs files, setup the ant task, and generate an
XML report that Hudson can then display.   See:

http://dev.eclipse.org/viewcvs/index.cgi/sourceediting/development/athena/org.eclipse.wst.xml.xpath2.releng/buildUtils.xml?view=markup&root=WebTools_Project

The only thing each project would need to do is specify the exclusion list, and
the location of where to scan the JAR or class files of it's particular files.

You can see an FindBugs report integrated with Hudson at:

https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp-wst.xsl.psychopath/

-- 
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


Back to the top