Yep, agreed. Both are useful:

- the dashboard is useful to compare projects (like when you have
several subprojects part of a bigger project)
- the historical data is useful to compare a project with itself across
time.

-Vincent

> -----Original Message-----
> From: Aslak Hellesøy [mailto:[EMAIL PROTECTED]
> Sent: 30 August 2003 18:00
> To: Maven Developers List
> Subject: Re: [idea] Multiproject Dashboard
> 
> Vincent Massol wrote:
> 
> >Hi,
> >
> >We have lots of very nice code quality reports: checkstyle, pmd,
simian,
> >findbugs, activity, jdepend, clover, etc. However, having these
reports
> >is not enough to make the problems go away.
> >
> >One idea that may help is to provide a global dashboard for all
projects
> >(as part of the multiproject plugin). For example:
> >
> >
> >Project name | Checkstyle | Clover | PMD | ... |
> >
> >Project1     | 500        | 60%    | 70  | ... |
> >Project2     | 1500       | n/a    | 35  | ... |
> >[...]
> >
> >(being able to sort on columns would be even nicer)
> >
> >Even better would be a "overall score" but that will probably be too
> >difficult to achieve and will make sense only for projects using the
> >same reports and the same rules inside each reports.
> >
> >Anyway, on my project at work we have several hundreds of projects
and
> >it's just downright impossible to get a nice view of all checks for
all
> >projects and see which project needs to get more quality focus than
> >others. Such a view would make it possible.
> >
> >My belief is that once we get that dashboard, some competition may
> >emerge between projects and people will start paying more attention
to
> >the reports.
> >
> >What do you think? Anyone fancy doing this? :-)
> >
> >
> I'd love to, but I've got too many things going. But the feature I
> really want to see is historical data of these metrics.
> That way, it is possible to generate graphs showing various trends in
> the codebase.
> 
> This is a lot more valuable than just looking at a static snapshot of
> the current codebase. You get a feel of
> when code coverage dropped, code duplication increased etc.
> 
> Now I think this is a separate project, and should be decoupled from
> Maven.
> 
> Aslak
> 
> >Thanks
> >-Vincent
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
> 
> 
> --
> http://blogs.codehaus.org/people/rinkrank/
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



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

Reply via email to