[
http://jira.codehaus.org/browse/MFINDBUGS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265525#action_265525
]
Garvin LeClaire commented on MFINDBUGS-110:
-------------------------------------------
Our project with a high threshold did not slow on version 1.3.9 but medium or
normal did. It can vary by the project and code size.
After that the plugin does not have any control on the length of time findbugs
takes. The fork option typically will only affect multimodule projects with a
small amount of code to check in each module.
You can use the 2.3.3-SNAPSHOT version and set the trace option for findbugs to
get output of the findbugs run.
> Major performance degradation since FindBugs plugin 2.1
> -------------------------------------------------------
>
> Key: MFINDBUGS-110
> URL: http://jira.codehaus.org/browse/MFINDBUGS-110
> Project: Maven 2.x FindBugs Plugin
> Issue Type: Improvement
> Affects Versions: 2.2, 2.3
> Reporter: Christoph Kutzinski
> Assignee: Garvin LeClaire
> Priority: Minor
> Fix For: 2.3.2
>
>
> Since FindBugs plugin performance got much worse.
> E.g. for a small multimodule project with 3 modules execution time increased
> from ~50 sec to ~ 1 min 20 sec
> For a big project with 30 submodules it increased from ~ 4 min to ~ 8 minutes
> - i.e. execution time has doubled!
> See also MFINDBUGS-104
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
