Max Bowsher wrote:
Daniel Kulp wrote:
Dan,
I'm cannot really answer the question about what @aggregator does, but I
can say the javadoc example is not a good one. There are many of us that
think the javadoc mojo should NOT have it and have our javadoc plugins
locked down to a previous version for the same reason. With @aggregator,
javadoc causes the buil to take HOURS in a multi-module build due to the
@aggregator stuff.
Speaking of which, is there any light at the end of the tunnel regarding
ending this non-optimal situation?
I will note that simply dropping @aggregator from surefire-report seems to
have done the right thing as far as I can tell, but I'd like someone who
knows anything about this to pipe up before I check it in that way.
Based on preliminary research, I hypothesize that @aggregator is simply
broken so it's therefore not needed on any plugin, including javadoc.
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
