| Care to elaborate? Why unreadable?
Yes, I'm also interested in the arguments for that.
At the moment I'm responsible for a relatively big build environment
that is using ANT and also has
its fair amount of reporting done. Using ANT's functionality for
macro's, subant and what have
you the final reporting result consists of "two" pages. One for my
aggregated reports, and
one for each module's "own" reports. My experience is that nobody is
actually reading/interested
in the module's own reporting and only browsing the aggregated reports.
I'm currently revisiting Maven to see whether version 2.0.4 is something
I could
use in my next engagement, but am a bit disappointed by the whole multi
module
reporting part of it. It seems to me that "convention over
configuration" hasn't
gotten through to that section yet - as there is no real convention about
multi module reporting. What I would like to see is a standardized way
for this.
So for instance, each report should support a "aggregate" configuration
setting.
Torsten Curdt wrote:
Not all plugins support aggregation, though, and I'm not sure if that's
desirable (i.e. the surefire report, if it's aggregated it might become
unreadable).
Care to elaborate? Why unreadable?
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Cumquat Information Technology
De Dreef 19
3706 BR Zeist
T +31 (0)30 - 6940490
F +31 (0)30 - 6940499
http://www.cumquat.nl
[EMAIL PROTECTED]
M +31 6 51 169 556
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
