I've seen this on builds before albeit with Maven 1. I believe this happens when the build creates a large number of classloaders which are not garbage collected quickly enough (or when there are class reference leaks). The workaround was the same as the one you show (at least for the Sun JVM).
This may be an indicator that we have a classloading issue. -- Jeremy On 4/29/06, Rick Rineholt <[EMAIL PROTECTED]> wrote:
I received the below error on builds .. added the following javac arguments to mvn.bat to resolve: -XX:MaxPermSize=128m -XX:PermSize=64m Don't ask me what, or why answer provided via Googling. YMMV [INFO] Compilation failure Failure executing javac, but could not parse the error: The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: PermGen space
