Actually, this problem was mentioned a couple of times before. I have the same headache as the "generate-source" phase is called again, which in my case caused the whole source generatred again!
the defect is in javadoc plug-in's defects list on JIRA ( http://jira.codehaus.org/browse/MJAVADOC-137). It seems to be caused by @aggregator in the javadoc 2.3. Maybe, we could downgrade it to version 2.2and try? I'm interested in knowing if it can solve the problem ... On 1/26/08, Roland Asmann <[EMAIL PROTECTED]> wrote: > > So, I went home after this mail last friday, and happened to stumble by > the > company today at this early hour. The site-build has finished, and has > taken > a grand total of 818 minute, which roughly translates into 13,6 hours!!! > > Is it really necessary to run the mentioned plugins as aggregators? I find > it > hard to believe that nobody has mentioned this before, because this will > make > things impossible for projects that are a little larger than average or > have > lots of/slow tests! > > > On Friday 25 January 2008 19:31, Roland Asmann wrote: > > Hi all, > > > > Is there a way to tell Maven to NOT run several of the reporting-plugins > in > > aggregate-mode? > > > > At the moment, I am trying to build the sites to my project, which is > > taking FOREVER! I've written down the times that Maven is taking for > > several different calls, and I feel the reporting it taking way too > long. > > > > If I run my project with 'mvn clean install', it takes about 13 minutes > to > > complete. When I throw out the tests, it needs just under 2 minutes. > > However, if II try to run the site ('mvn clean site'), maven uses ages > to > > complete (not sure yet how long, it has been running for over 4 HOURS > > already, and still no clue as to how long it will take!). > > > > Yes, I know my project is big. It's a multi-module project with about 60 > > modules, but I don't think they should be split into smaller projects. > > Besides, the normal build has an acceptable time-frame (especially if we > > skip tests like we do during development), so I feel no need to split > them. > > > > So, the plugins I've found to trigger in aggregate mode (although I have > no > > idea why they should) are: > > - javadoc:javadoc (not using the aggregate-parameter, so why trigger it > > this way?) > > - surefire-report:report > > - surefire-report:report-only > > > > Any help would be greatly appreciated! > > -- > Roland Asmann > > CFC Informationssysteme Entwicklungsgesellschaft m.b.H > Bäckerstrasse 1/2/7 > A-1010 Wien > FN 266155f, Handelsgericht Wien > > Tel.: +43/1/513 88 77 - 27 > Fax.: +43/1/513 88 62 > Email: [EMAIL PROTECTED] > Web: www.cfc.at > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
