The following comment has been added to this issue:
Author: Vincent Massol
Created: Tue, 18 Nov 2003 2:48 PM
Body:
In my first implementation of the dashboard (which I never committed) I started
implementing the different aggregators in the related project themselves (in the cs
plugin for cs aggregators, etc). However, I soon found out that I didn't want to mess
with exsiting plugins so that they would provide information useful only for the
dashboard.
My second implementation (the one in CVS) has thus focused on remaining completely
independent of plugins themselves. I much prefer this even if it's less
"object-oriented".
Also, the dashboard features do not seem general enough to warrant a change of the POM.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPDASHBOARD-1
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPDASHBOARD-1
Summary: Dashboard should use aggregators from associated plugins
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-dashboard-plugin
Assignee:
Reporter: Sean Timm
Created: Tue, 18 Nov 2003 11:31 AM
Updated: Tue, 18 Nov 2003 2:48 PM
Description:
The currently available aggregators are all defined and made available within the
dashboard plugin itself. I'd like to see aggregators made available through their
associated plugin instead. Since this is specific to reporting, it seems like it
would be nice to be able to define which ones to use within the report tag itself
(though properties would work, too). Of course, the semantics of the report structure
would have to change from its currently limited functionality. For example:
<reports>
<report provider="maven-dashboard-plugin">
<aggregator provider="maven-clover-plugin">
<include>clovertpc,cloverloc</include>
</aggregator>
<aggregator provider="maven-checkstyle-plugin">
<exclude>cswarnings</exclude>
</aggregator>
<!-- Defaults to *all* defined aggregators in the plugin -->
<aggregator provider="maven-cactus-plugin" />
</report>
</reports>
I realize that Maven doesn't currently use attributes in the project.xml, so you could
do it a wordier, uglier way, too... ;)
With something like this, the dashboard plugin could query the specified aggregator
providers for their available aggregators and then generate the appropriate report.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]