Is the idea to capture detailed information for each plug in or just
high level statistics like the old dashboard used to do?
What I have in place today, is a simple class that has the project id
(from the pom), stat id (defined by the parser), value (I'm using Number
here to allow for flexibility). The idea of the stat id is that a
single plug in can generate multiple stats like the checkstyle plug in
currently generates number of files, errors, warnings, etc.
One thing that I'd like to avoid is to run the reports more than once.
In other words, if the surefire report was already ran, just capture the
stats from it.
How would you pass information from one report back to the "dashboard"
report? I've been trying to figure out this from the documentation but
has not been able to find it out yet...
I'm very willing to help, just don't know where to start :)
Mauro
Brett Porter wrote:
Mauro Botelho wrote:
Did anybody put any more work on this?
No, not yet. I'm thinking of spending some time on it soon.
I started to look at Brett's suggestions, but could not link the names
to the classes.
Looking at some of the plugins (Surefire, checkstyle and pmd) I think
that when Brett mentions that we have the parsers, I think he's talking
about the PmdReportListener, CheckstyleReportListener and an instance of
org.codehaus.surefire.report.Reporter for example. Is that correct?
Basically, yes.
Currently most of the plugins hardcode their "parsers" based on specific
rules. To force the plugins to create and maintain the parsers might be
too intrusive.
These will always be necessary to produce a feature rich report.
Probably what we need is a common set of aggregation data points that
the parsers can filter these into.
Is there a lower level that we could use for this integration? Was it
the intention to use a different SiteRenderer for this?
I dont think it would be a site renderer, but another report.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
