[
http://jira.codehaus.org/browse/MOJO-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92591
]
Garvin LeClaire commented on MOJO-732:
--------------------------------------
I think the data should be stored in a database and detail is important if we
wish to truly understand our code quality history.
The current way where QALab and the dashboard plugins are required to gather
information throughout different disk levels of the project is some what
kludged (sp?). It requires that these plugins know about all the various
plugins output formats.
A more ideal situation would be to have the plugin writers be able to create
output to a standard data model. I think we are trying to accomplish a similar
task as outline by the ISO9126 ( http://en.wikipedia.org/wiki/ISO_9126 )
standard attempts to address.
This allows the history information to be shared with a wider audience since
databases are easier to scale than file systems. This does allow for more
flexible and dynamic reporting options.
Here are a few ideas I have on items to help address these:
1. Develop a data model for the database.
2. Create a Doxia sink writer to write to a database
3. Future "code quality" plugins would need to modify output options to
support this infrastructure if they currently do not support multiple sinks.
4. A scanner plugin could be developed to scan the different text outputs.
This could be used in the interim. It should have the ability to build file
format extensions for the different report layouts. The maven-enforcer plugin
looks like a good example.
I would be willing to use the Findbugs plugin I work on to implement a plugin
update to support this. I think we could also look at the checkstyle, PMD, and
JDepend plugins.
I think we should look at starting a page on the Codehaus wiki if we want to
put further design ideas and information for others to see and validate.
Garvin LeClaire
> 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
