[ http://issues.apache.org/jira/browse/GERONIMO-761?page=comments#action_12316152 ]
Aaron Mulder commented on GERONIMO-761: --------------------------------------- Could the plugin problem be caused by plugins generated by the M4 branch that are unavailable during a clean build of HEAD or vice versa? > Transient failures during full rebuild (OOM?) > --------------------------------------------- > > Key: GERONIMO-761 > URL: http://issues.apache.org/jira/browse/GERONIMO-761 > Project: Geronimo > Type: Bug > Components: buildsystem > Versions: 1.0-M3 > Reporter: Aaron Mulder > > I can't often run a full "maven -o m:rebuild-all" and make it all the way > through. Usually, it dies around the time of the Geronimo assembly module. > The errors vary, but include: > - bootstrap:bootstrap null > - error in plugin script > A subsequent "maven -o" completes successfully (having it skip tests/itests > to begin with also works), leading me to believe that somehow the amount of > work starves the VM of something, probably memory, but slightly smaller > quantities of work don't. Though after the plugin error the next build > complains about a bad plugin cache and has a lot of stack traces complaining > about JEXL errors, but after that things are back to normal. > Someone reported a similar error to the user or dev list, but I think their > message was still different from mine. > This happens to me on Linux (SuSE Pro 9.3) with JDK 1.4.2_08 and on Mac (OS X > 10.4.1 and 10.4.2) with JDK 1.4.2_07. I have not tried extending the Maven > memory settings like we used to recommend for JDK 1.5. > I wonder if making more of the tests fork would help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
