Dion Gillard wrote:
Generally looking for patterns about where it's failing. e.g. always during xdoc or always during XXX.
In my case, I was getting java.io.IOException: failed to allocate memory when launching javadoc.
This problem was strictly related to the amout of xdocs transformed to html up to that point. Disabling plugins that generated many xdocs (like statcvs plugin) made it disappear.
Dion, please take a look at my analysis in http://jira.codehaus.org/browse/MAVEN-1294
xdoc transformation leaks huge amounts of memory. All TagScript objects ever instantiated stay permanently glued to app main thread. Same thing for JellyContext local XML parsers (!!!) - they never get GCed.
Jason argued that Jelly is broken beyound repair, and we should wait for the lightweight xdoc transformer from m2 to be backported to m1.
Rafal
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
