Hi Mike, On 8/16/06, Mike Perham <[EMAIL PROTECTED]> wrote:
Hilco, your proposal sounds good in the context of a single VM invocation when everything is in-memory. How does this extend to reporting over time?
I was referring to Arnaud's idea of a versioned database for such data. Obviously, the data in the graph would have to come from somewhere. :-) Or did you mean the weighted sum thing? That was definitely meant as part of a full build, you'd need all reporting done before this weighted sum can be calculated.
Just as a compiled binary is a "binary snapshot" of the code at a point in time, we need to take a "report snapshot" with all this metadata persisted for reporting on a module over time. Perhaps each report could optionally generate their own OWL metadata which can be packaged by site into a "reporting archive" JAR and stored in the repo for each version of a module. We would need a version-based reporting API to trawl over those versions.
Yeah, I guess that would work too. What does OWL stand for? Cheers, Hilco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
