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.
Dan On Tuesday 05 February 2008, Dan Fabulich wrote: > Dumb question (possibly): what does the @aggregator annotation do, > exactly? > > I read the doc here: > http://maven.apache.org/developers/mojo-api-specification.html > > It says: "Flags this Mojo to run it in a multi module way, i.e. > aggregate the build with the set of projects listed as modules." > > But I don't understand that. What does it mean to aggregate the build > with its modules? What's a multi-module way? > > Specifically, in 2.4 I added @aggregator to the surefire-report plugin > when I tried to fix SUREFIRE-268 by copying code from the javadoc > plugin, but this appears to have caused SUREFIRE-449: in a 10 project > reactor, project 1's tests are run 10 times; project 2's tests are run > 10 times, project 3's tests are run 10 times, and so on. > > It seems like getting rid of the @aggregator I added in fixes the > problem, but I don't really understand why I added it in the first > place, or why the javadoc plugin has it, or why jxr doesn't. > > How is it supposed to work? > > -Dan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
