[
http://jira.codehaus.org/browse/MOJO-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garvin LeClaire updated MOJO-882:
---------------------------------
Priority: Minor (was: Major)
Issue Type: New Feature (was: Bug)
Summary: allow findbugs plugin to output XML format the same as findbugs
xml format in addidtion to the xdoc format. (was: findbugs-maven-plugin XML
format does not follow same schema as that generated by findbugs)
Findbugs Maven plugin currently outputs xml in the xdoc format. This is
consistent with the format produced by Findbugs -xdoc option.
This provides backwards compatibility with Maven 1 plugin.
There is a request to dump the raw xml that findbugs produced when the -xml
option is used or to modify the xdoc output to contain source file location
information. Though this information is in the POM there is a benefit to
having it included in the findbugs plugin report.
> allow findbugs plugin to output XML format the same as findbugs xml format in
> addidtion to the xdoc format.
> -----------------------------------------------------------------------------------------------------------
>
> Key: MOJO-882
> URL: http://jira.codehaus.org/browse/MOJO-882
> Project: Mojo
> Issue Type: New Feature
> Components: findbugs
> Reporter: Stephen Connolly
> Assignee: Garvin LeClaire
> Priority: Minor
> Attachments: 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
