[ 
http://jira.codehaus.org/browse/MFINDBUGS-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124232
 ] 

Ulli Hafner commented on MFINDBUGS-22:
--------------------------------------

Thanks, the new SNAPSHOT version works like a charm!

> allow findbugs plugin to output XML format the same as findbugs xml format in 
> addidtion to the xdoc format.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MFINDBUGS-22
>                 URL: http://jira.codehaus.org/browse/MFINDBUGS-22
>             Project: Maven 2.x FindBugs Plugin
>          Issue Type: New Feature
>            Reporter: Stephen Connolly
>            Assignee: Garvin LeClaire
>            Priority: Minor
>         Attachments: mojo-882-b.patch, mojo-882.patch
>
>
> The XML report generated by findbugs-maven-plugin is a completely different 
> schema from that generated by findbugs natively.
> The files generated by the plugin have the same initial element (thus making 
> it difficult to differentiate between the two formats) but the schema layout 
> and elements are different.
> This is because the findbugs-maven-plugin does not delegate to the findbugs 
> xml reporter, but instead generates the xml report internally.
> Initial discussion: http://www.nabble.com/Findbugs-maven-plugin-tf4239159.html
> If the internally generated format is used by other projects, either a config 
> option to enable the findbugs xml generator or the output of the maven 
> sourcepaths in the findbugs-maven-plugin xml report would be sufficient 
> patches for our needs.
> The long term fix should be to output in the findbugs native format... thus 
> people would not have to write two sets of parsers (one for maven invoked 
> findbugs and the other for all other invokations of findbugs)
> The advantage of the internally generated xml report is that it removes 
> dependency on the schema changes that the findbugs has been known to make.

-- 
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


Reply via email to