[
http://jira.codehaus.org/browse/MOJO-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93337
]
Jörg Hohwiller commented on MOJO-732:
-------------------------------------
I think that we should think about the way the plugin will work at the end of
the day.
1. If a static website is build via mavens site generation there is no real
need for storing all defects in detail and require a business-intelligence
system.
2. If the website should be dynamic, there could be many advanced features and
on demand queries and reports. This would either cause that the plugin has a
goal that starts a servlet-container (e.g. jetty) or comes with an extra piece
of software (war-file) that is no maven plugin and can be hosted on the
projects website.
I personally think that a simpler approach (like 1.) would make more sense
here. Many projects do NOT have a hosting plattform that can run servlets and
running the thing locally on the client is NOT really cool.
At the end of the day most of the users are interested in the defects that they
have NOW and the historical devolution of the defects.
Who really needs to know about each individual defect that was raised month ago?
The only problem could be that the configurations (of checkstyle, findbugs,
etc.) might be changed over the time and then the measured defects are not
compareable anymore. Anyhow I would store the defects agregated but NOT per
tool (checkstyle, findbugs, ...) but per sensor (checkstyle.WHITESPACE_AROUND,
checkstyle.PARAMETER_ASSIGNMENT, ..., etc). To use a normalized format and
create a transformation from the tool-specific output to the normalized format
will make sense. Then the solution can still work if the tool gets upgraded and
the output format changes.
I do not know QALab... Do we reinvent the wheel here? What will dashboard do
what QALab can not do?
> 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
