Brian E. Fox wrote:
The trouble is the javadoc goal is bound in the release profile which is getting activated when people do releases. IMO we should put javadoc back the way it was in 2.4 [...]
I don't think that r661899 is the cause for the regression and hence it wouldn't make sense to revert it.
AFAIK, the problem is not forking by itself but the combination of forking with aggregating. For instance, the source:jar goal employed by the release profile forks, too, but to my knowledge doesn't cause problems. In Javadoc Plugin version 2.5, neither javadoc:jar (invoked during "package" phase) nor javadoc:javadoc (invoked during "site" phase") are forking aggregators. The only forking aggregators are the new javadoc:*aggregate goals.
Unless we have a build log or an IT to prove that javadoc:*javadoc is causing the regression, I feel we're better off to tweak the new goals.
Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
