Also i am using following profile to run findbugs (only in user.core).

<profile>
      <id>findbugs</id>
      <activation>
        <property>
          <name>findbugs</name>
          <value>true</value>
        </property>
      </activation>
      <build>
        <plugins>
          <plugin>
            <groupId>org.codehaus.mojo</groupId>
            <artifactId>findbugs-maven-plugin</artifactId>
            <configuration>
              <effort>Max</effort>
              <threshold>Low</threshold>
              <xmlOutput>true</xmlOutput>
              
<excludeFilterFile>user-core-findbugs-excluded.xml</excludeFilterFile>
            </configuration>
            <executions>
              <execution>
                <phase>verify</phase>
                <goals>
                  <goal>check</goal>
                </goals>
              </execution>
            </executions>
          </plugin>
        </plugins>
      </build>
    </profile>

This is not much of a help when running findbugs for the first time. But 
will be helpful, after module has been fixed and making changes to files 
afterwards. If we do a build by enabling above profile, build will fail 
if there are findbugs errors.

Thanks
AmilaJ


Afkham Azeez wrote:
> Without the IDE fixing things will be a bit messy. What I do is run 
> FindBugs on selected modules, and then rank them based on severity, 
> and then fix the ones with highest severity first, and so on, and try 
> to attain zero bugs status. The bug commentary should give you a good 
> idea about how to fix the bug. After a module has been fixed, before 
> committing the code, we need to make sure that we run FindBugs on the 
> changed files. There is an option to run FindBugs only on the changed 
> files.
>
> Azeez
>
>
>
> On Wed, Sep 1, 2010 at 4:32 PM, Samisa Abeysinghe <[email protected] 
> <mailto:[email protected]>> wrote:
>
>
>
>     On Wed, Sep 1, 2010 at 4:31 PM, Samisa Abeysinghe <[email protected]
>     <mailto:[email protected]>> wrote:
>
>         Can you tell how to run find bugs (the options) and what to
>         capture?
>
>
>     I meant running it without IDE 
>
>
>         On Wed, Sep 1, 2010 at 3:42 PM, Afkham Azeez <[email protected]
>         <mailto:[email protected]>> wrote:
>
>             Folks,
>             Now that everybody is back from vacation, we can start on
>             this. It may not be necessary to do this in hackathon mode
>             (anyway, there is no space right now because of the office
>             refurbishment work). Each one of the volunteers can start
>             working on their components right away.
>
>             Azeez
>
>
>
>
>             On Tue, Aug 17, 2010 at 3:40 PM, Afkham Azeez
>             <[email protected] <mailto:[email protected]>> wrote:
>
>                 Team,
>                 I have created a spreadsheet which lists all the
>                 components. Please put your name in the owner field if
>                 you'd like to work on the relevant components during
>                 the hackathon. Hope to see a lot of enthusiasm :)
>
>                 
> https://spreadsheets.google.com/a/wso2.com/ccc?key=tigDdt9SQHTfLz4tyLlrL3A&hl=en#
>                 
> <https://spreadsheets.google.com/a/wso2.com/ccc?key=tigDdt9SQHTfLz4tyLlrL3A&hl=en#>
>
>                 Thanks
>                 Azeez
>
>                 On Mon, Aug 16, 2010 at 11:14 AM, Afkham Azeez
>                 <[email protected] <mailto:[email protected]>> wrote:
>
>                     Team,
>                     Will it be a good idea to have a 2 day FindBugs
>                     hackathon? Yesterday, I ran FindBugs on
>                     org.wso2.carbon.core. When I started, the bug
>                     count was about 60, and believe me, most of those
>                     were really potential bugs, some major such as
>                     unclosed files, potential deadlock situations and
>                     so on. I was also able to learn quite a bit by
>                     reading the bug commentaries. Now the bug count is
>                     down to about 20.
>
>                     During this hackathon, each person can select a
>                     number of components they are familiar with or
>                     have worked on before, and start improving it. I
>                     also think it will be beneficial if we could run
>                     FindBugs on the changed files before committing.
>                     It can be done using the IDEA/Eclipse plugin.
>
>                     We can arrange a convenient date, perhaps in the
>                     first week of September after everybody comes back
>                     from their vacations. 
>                     Thoughts welcome.
>
>                     Thanks
>                     -- 
>                     Afkham Azeez
>                     Senior Software Architect & Senior Manager; WSO2,
>                     Inc.; http://wso2.com, Lean . Enterprise . Middleware
>                     Member; Apache Software Foundation;
>                     http://www.apache.org/
>                     email: [email protected] <mailto:[email protected]>
>                     cell: +94 77 3320919
>                     blog: http://blog.afkham.org
>                     twitter: http://twitter.com/afkham_azeez
>                     linked-in: http://lk.linkedin.com/in/afkhamazeez
>
>
>
>
>                 -- 
>                 Afkham Azeez
>                 Senior Software Architect & Senior Manager; WSO2,
>                 Inc.; http://wso2.com, Lean . Enterprise . Middleware
>                 Member; Apache Software Foundation; http://www.apache.org/
>                 email: [email protected] <mailto:[email protected]> cell:
>                 +94 77 3320919
>                 blog: http://blog.afkham.org
>                 twitter: http://twitter.com/afkham_azeez
>                 linked-in: http://lk.linkedin.com/in/afkhamazeez
>
>
>
>
>             -- 
>             *Afkham Azeez*
>             Senior Software Architect & Senior Manager; WSO2, Inc.;
>             http://wso2.com, 
>             /
>             /
>             /Member; Apache Software Foundation;
>             //http://www.apache.org///
>             email: //[email protected]/ <mailto:[email protected]>/ cell:
>             +94 77 3320919
>             blog: //http://blog.afkham.org//
>             twitter: //http://twitter.com/afkham_azeez//
>             linked-in: //http://lk.linkedin.com/in/afkhamazeez/
>             /
>             /
>             /Lean . Enterprise . Middleware/
>
>
>             _______________________________________________
>             Carbon-dev mailing list
>             [email protected] <mailto:[email protected]>
>             https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>         Thanks,
>         Samisa...
>
>         Samisa Abeysinghe
>         VP Engineering
>
>         WSO2 Inc. 
>         http://wso2.com
>         http://wso2.org
>
>          
>
>
>     Thanks,
>     Samisa...
>
>     Samisa Abeysinghe
>     VP Engineering
>     WSO2 Inc. 
>     http://wso2.com
>     http://wso2.org
>
>      
>
>
>
>     _______________________________________________
>     Carbon-dev mailing list
>     [email protected] <mailto:[email protected]>
>     https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
>
> -- 
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, 
> /
> /
> /Member; Apache Software Foundation; //http://www.apache.org///
> email: //[email protected]/ <mailto:[email protected]>/ cell: +94 77 3320919
> blog: //http://blog.afkham.org//
> twitter: //http://twitter.com/afkham_azeez//
> linked-in: //http://lk.linkedin.com/in/afkhamazeez/
> /
> /
> /Lean . Enterprise . Middleware/
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>   


_______________________________________________
Carbon-dev mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to