[ http://jira.codehaus.org/browse/MSITE-189?page=comments#action_80669 ] Kay Grosskop commented on MSITE-189: ------------------------------------
Hoi we have also made our proprietary Dashboard plugin. I hope to convince my manager soon to be able to contribute to a common effort. I think it does not make sense to invent this many times. I havn't had time yet to investigate the qalab & radar functionality and source in depth. By the time we wrote our plugin the state of the project was unclear. Anyhow our plugin features: - aggregation of a number of results from submodules in a multi-module project. (findbugs,checkstyle,junit,cobertura,ncss) - history charts on the collected data. I think the issue 188 is not really to the point here. The problem is, as far as I understand, that on multimodule projects the maven engine wil go through the reporting fases of the submodules and there is no hook to do a data aggregation and chart generation step afterwards. It seems to be a feature of the maven build lifecyle. the workaround for us was not to define the dashboard-plugin as a report plugin at all, but to run it after the site generation. like mvn site dashboard-plugin:collect site:deploy I also see the aggregation and history as two conceptually different tasks. The first should be resolved on a more generic level in a way that makes it easier for plugin writers to aggregate their data on multimodule builds (currently it seems that only javadoc en ncss knew to hack their way ) The history collection and chart generation should be the core of concern of a dashboard/history plugin. what do you think. > Coordinate the efforts of several users to write a Dashboard Plugin for Maven > 2 > ------------------------------------------------------------------------------- > > Key: MSITE-189 > URL: http://jira.codehaus.org/browse/MSITE-189 > Project: Maven 2.x Site Plugin > Issue Type: Task > Reporter: Gisbert Amm > Attachments: screenshot-1.jpg > > > Coordinate the efforts of several users to write a Dashboard Plugin for Maven > 2 > Several people started their own Dashboard plugins (see > http://jira.codehaus.org/browse/MSITE-188 and discussions on the users > mailing list). It would be better, if one of those implementations would be > adopted by the Maven team and the various development efforts would be > coordinated and focused to that one. -- 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
