RE: [Cobertura-devel] javanscc jar dependencies ?

[Mark D. <Mar...@sa...>]

 > -----Original Message-----
> From: cob...@li...=20
> [mailto:cob...@li...] On=20
> Behalf Of Czechowski, Igor
> Sent: Wednesday, May 18, 2005 11:56 AM
> To: Cobertura-devel
> Subject: RE: [Cobertura-devel] javanscc jar dependencies ?
>=20
> I came up with the two ideas.=20
>=20
> First, what do you think about including other source code metrics
> javancss provides in the cobertura report ?

I'm not sure I see a big advantage to that.  I think I'd rather see work =
being done more toward fixing the bugs that already exist, than toward =
merging in lots of code that isn't really related.

I'm not against having a nice, unified view of lots of fancy metrics, =
but I think that would be handled better as an independent project than =
as an addition to Cobertura.  I guess I'm a student of the "write a =
program to do one thing and do it well" mentality.

> So the scenario would be to produce the entire html report=20
> and only the
> package overview of the xml one. Then I would use transformation to
> produce the html page for the cruisecontrol. I can merge the existing
> xml report but I thing it's a little bit over reporting for me at the
> current state.

Hmm.  I guess you could accomplish something along these lines by =
generating the XML report then merging it into the CruiseControl build =
log (the same way Junit XML is merged).  Then you would need to add an =
xsl transform for displaying a coverage summary to the CruiseControl =
build results page.

-Mark