Try the 1.1-SNAPSHOT as I know it works.  I cannot remember if I fixed this
for 1.0.0.

I did not use Findbugs xml because of the way the original Maven 2 plugin
was started.  It was easier to write one and I have more options for adding
more wirter the way it is currently written.   I was the one who wrote the
original xml reporter for FindBugs when I worked on the Maven 1 plugin.




--
Regards,


Garvin LeClaire
[EMAIL PROTECTED]







On 4/2/07, dvicente <[EMAIL PROTECTED]> wrote:


any news ?

one question, why the ifndbugs-maven-plugin generate its own xml instead
of
let findbugs do the job ?

Garvin LeClaire-2 wrote:
>
> Which version of the Findbugs plugin are you using?
> Are you able to send me the findbugs.xml file?
>
>
>
>
> --
> Regards,
>
>
> Garvin LeClaire
> [EMAIL PROTECTED]
>
>
>
>
> On 3/28/07, dvicente <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hi,
>>
>> for my dashboard-maven-plugin, i want to parse the xml result file of
>> findbugs.
>>
>> Does anyone know if exist a parser in the API to retreive all objects
>> structure without to parse the file as a simple xml file ?
>>
>> the findbugs-maven-plugin generate xml file in wrong format .
>>
>> it generates messages as "Error analyzing public void <init>" where
init
>> is
>> a method and do a parseException.
>>
>> Does anyone know to correct that ?
>> --
>> View this message in context:
>>
http://www.nabble.com/-m2--findbugs-xml-parser-tf3479394s177.html#a9710627
>> Sent from the Maven Developers mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>

--
View this message in context:
http://www.nabble.com/-m2--findbugs-xml-parser-tf3479394s177.html#a9788933
Sent from the Maven Developers mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to