Hi, I've had this idea for a while. I prefer to bring it up on the dev mailing list instead of issue tracker, because I work offline most of the time, and because I wanted to get some feedback before creating an issue.
My primary intent would be to gather info from the build and store them into a DB. The info would be generated from the different plugins. For example: nb of lines of code, number of bugs found by findbugs, etc... At each build, this data is already gathered, but in different places by different plugins. At least in the maven version I am using (1.0rc2). I want to centralize and store it. I've seen things in the dev list talking about multi-projects and dashboard. Maybe those are related? (I couldn't find much information about those in my personal archives). I've got the maven 1-0-rc3-snapshot PDF doc from the 30th of March but it says nothing about those. 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]
