Good day, * What would be the main difference between the reporting phase(s) and the site phases? the former are for reports while the latter are for the documentation? What about reports about the documentation? * As for when, maybe it should be before packaging so that users will have the option to package the report as well ( if they need to do so ). But if there would be reports that run on the assemblies, then this would not work.
Just my 2 cents worth :-) - Franz On 1/30/07, Brett Porter <[EMAIL PROTECTED]> wrote:
I think that makes sense. I wouldn't go with post-reporting, though, as there is no 'reporting' phase - they happen when it's appropriate (process-sources, test, etc). Maybe for consistency having: generate-reports (for all those that haven't executed yet) process-reports (could aggregate them here) ... just before the package phase? (Or maybe later, before install, after integration test). I think moving more towards having these as part of a standard build instead of the whole site + fork thing is the way to go, and then just being able to turn them on or off as needed. The only concern is whether they can make sense concurrently sometimes (especially your code coverage ones that mangle the class files :) Cheers, Brett On 31/01/2007, at 9:38 AM, Joakim Erdfelt wrote: > I'd like to see a discussion start on adding the possibility of a new > phase into the default lifecycle. > > A reporting-aggregate that executes at the end of all standard > reports. > (Could also call it post-reporting) > > I can see the Dashboard Report, QA Labs, and even a standard reporting > framework utilizing this phase to perform some needed tasks. > > - Joakim > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
