[
http://jira.codehaus.org/browse/MOJO-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MOJO-882:
----------------------------------
Attachment: mojo-882.patch
Patch for Option a.
This changes the schema output by findbugs-maven-plugin to insert the following
directly after <BugCollection>:
<Project>
<SrcDir>maven source root</SrcDir>
<SrcDir>maven source root</SrcDir>
<SrcDir>maven source root</SrcDir>
</Project>
this allows parsing the file to determine where the source code is from.
The changes to the schema are following the schema used by findbugs natively...
so should not cause too much screaming.
(I have a second alternative patch where I provide the native findbugs xml
output... will attach that when I've reset my copy of the source tree and
recreated it... as I had lots of fun with IntelliJ removing trailing spaces and
making the patch massive)
> findbugs-maven-plugin XML format does not follow same schema as that
> generated by findbugs
> ------------------------------------------------------------------------------------------
>
> Key: MOJO-882
> URL: http://jira.codehaus.org/browse/MOJO-882
> Project: Mojo
> Issue Type: Bug
> Components: findbugs
> Reporter: Stephen Connolly
> 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
