I was thinking about something like this. I vas trying to build a plugin that should as a "site" postGoal It works this way:
For ecah "*-report.xml" file in target/generated-doc it search a coresponding stylesheet (jsl in plugin-resources) and applies it. It then concat the result of all those stylesheets to a merged-repport.xml that could be formated by xdoc and becomes the project summary on the site. It couls also be saved as timestamp or in DB. Another plugin / tool could extract from timestamped infos the repports evolution : number of checkstyle rules violation per line of code for example... Nico. > > One way I could see this working would be by: > > - having this plugin create a raw property file in the target dir, with > a property containing the data timestamp (perhaps need another one to > contain the date format to parse it out?) > > - let every plugin the possibility to add some data to this file. My > understanding is that the plugins are not run in parallel, so there is > no problem writing sequentially to the property file. > > - a summary page is made out off that information. > > - that information is stored into a DB. > > There are probably different ways to architect that plugin, and using a > property file is perhaps not the best thing. I've just tried to find a > simple solution that could work. My main idea was to not make this new > plugin dependent on the others, but rather the other way around. > > >From the DB, graphes can be generated to check the evolution of the > project. (one cool graph could be to have the evolution of the code size > against the effort put, such as described in Mythical Man-Month, but > that would require have the number of hours spent by the different > developers. This diagram is probably not very appropriate for open > source projects, but for more closed projects it would fit well.) > > One thing to keep in mind, is that it would be nice to be able to script > maven to retroactively build statistics, e.g. for the first time, or > when a new type of data is to be added to the stored information. That > means that the task requires a timestamp argument, same timestamp used > to retrieve the code from the source repository. > > > So now that I've described the idea, I would like to know: > > - is something like that already feasible? > > - if not would it make more sense for m2? > > - comments? Especially whether or not I should open an issue. > > Cheers, > > Jerome > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] Our name has changed, please update your address book to the following format for the latest identities received "[EMAIL PROTECTED]". This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
