Sorry for the delayed response. It's that time of year :)
Mauro Botelho wrote:
> Is the idea to capture detailed information for each plug in or just
> high level statistics like the old dashboard used to do?
I'd like each plugin to be able to have its own stats so they can easily
do some form of aggregation of their own content without having to
rewrite that code in every reporting plugin. However, having standard
elements that can be used to produce the dashboard would be very helpful.
>
> 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.
Sounds like a good start.
>
> 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.
That would be up to the plugin by determining the file exists and its
inputs haven't changed. Future versions of Maven will facilitate doing
this in a declarative way.
>
> 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...
The dashboard, as an aggregator, will have ${reactorProjects}. The
dashboard probably needs to know which files to aggregate from. Either
we'd use the plugin context here or have a standard naming scheme. I'm
not sure at this point.
>
> I'm very willing to help, just don't know where to start :)
>
Dig in if you find something that works for you! We can keep discussing
ideas here if it helps.
Thanks,
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
