-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, > I think the findbugs-maven report format is more appropriate to Maven. I > wrote both reporters and the Maven one seems to accommodate the other > plugins that require xml output such as dashboard, xradar and qaLab. > At this point we would need to get a consensus on any changes that would > impact other plugins. > You could create stylesheet to transform the format. What is it you are > trying to use the xml for? I also have a problem with this. As far as I can see the findbugs tool is capable of creating the XML output. The ANT task just calls the findbugs tool to create it. However the maven-plugin goes its own way. The problem is that the maven findbugs xml output is missing information that is available in the default xml format. Therefore you will not be able to create a stylesheet and do the transformation because the stylesheet can not magically figure out what is not already there... > > > I wrote the original findbugs xdoc writer as well as the Maven 2 version so > I do have a familiarity with the code if you have any questions. Okay so you are the perfect adressee for this toppic. Would you be willing to support an optional option to make the findbugs-plugin for maven create the default xml output format? Should I add a feature request to JIRA?
If I got you right, the format can not be changed generally because other tools like dashboard relies on the format as it is produces now. Is that correct? > > > -- > Regards, > > > Garvin LeClaire > [EMAIL PROTECTED] Cheers Jörg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGRP0amPuec2Dcv/8RAmqqAJ9npqfFt1rDUhuXwC9s8AZaf6aiWwCcD8YZ 77WIU8FQ/kqb/uG2yKbn574= =J4s7 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
