Stuart McCulloch wrote:
On 07/02/2008, Dan Fabulich <[EMAIL PROTECTED]> wrote:
Based on preliminary research, I hypothesize that @aggregator is simply
broken so it's therefore not needed on any plugin, including javadoc.
hmm, well I use @aggregator on some local mojos and it seems to do
what I expect, which is to build up a reactor for the current project and
its modules, and call the mojo once (whereas without @aggregator it
would call the mojo for each individual project in the reactor).
but this is based on trying out the various tags and a bit of delving into
the core maven code, so I might be off-base.
perhaps the issue you're seeing with @aggregator is caused by some
side-effect with @execute, which would fork a new life-cycle? so far I've
not seen anything like what you describe, but I don't use @execute...
If you unpack the attachment to SUREFIRE-449 and run this:
mvn clean site | grep "Maven Surefire Report"
you'll see that it's generating the Surefire Report three times, even
though the surefire-report plugin is definitely using @aggregator.
Dropping @aggregator fixes the problem.
I don't think @execute is to blame here, though it certainly could be; I
think it might simply be that @aggregator doesn't work with reporting
plugins...?
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
