[
http://jira.codehaus.org/browse/MOJO-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93007
]
Kriss commented on MOJO-732:
----------------------------
Well,
As Olivier said, I think that it's better to keep this dashboard devlopment
oriented and think about another plugin for more quality, ISO 9126 and report
question.
If we want to offer this kind of functionality, we don't just need to store
full data in a database, but also :
- manage refactoring : what to do if package/class/method moved or deleted,
- have a way to design a quality model, that's to say a mapping between ISO
9126 and metrics from PMD, JDepend and co
- provide a way to aggregate metrics data for a package/class/method or ISO
9126 category
- ...
So let's keep it simple and just provide a next step to this project by only
storing data currently used by the dashboard, but I like also the idea of
Stefan Seidel at the beginning of this post to store all xml report in the
maven repository as a jar. Today, every version or snapshot in the maven
repository can have its jar, source jar, test jar, source-test jar, let's add a
reports jar for further analysis.
> database support and historic view
> ----------------------------------
>
> Key: MOJO-732
> URL: http://jira.codehaus.org/browse/MOJO-732
> Project: Mojo
> Issue Type: New Feature
> Components: dashboard
> Reporter: David Vicente
> Assignee: David Vicente
>
> Hi all,
> i will start the database support for the dashboard-maven-plugin.
> I'll create a third view for each dashboard report to generate an history
> page with JFreechart time series graph representing the indicators's
> evolution.
> At this time, i generate an xml result file (dashboard-report.xml) which
> contains only aggregate results.
> If i send you this email, it is to synthesize your needs relating this
> historical view or quality statistics :
> - do I save in the base only the aggregated data coming from the dashboard
> xml result file
> - must I store the whole of the reports (cobertura, pmd etc...) and make the
> aggregation then
> i will use an external database (selected by the user) to make possible the
> base's re-use with another tool allowing more precise statistics than what
> could be made by the dashboard or to create statistics of projects wallet
> for example, to compare cobertura ratio between 5 projects.
> it could be interesting to create an issue in JIRA to follow this
> conversation?
> I await your answers impatiently.
> Thanks for your help.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
