Don't you have the full stack trace?
On Windows, it's easy to come out of resources since there are requirements for contiguous memory. You may try to compile right after boot, before running any other application which would fragment the memory.
The java.lang.StackOverflowError issue is often due to a thread stack size being greater than the JVM limit. Try to increase it with "-Xss" JVM option ("MAVEN_OPTS=-Xss1280k -Xmx...").
http://www.oracle.com/technetwork/java/hotspotfaq-138619.html states:
In Java SE 6, the default on Sparc is 512k in the 32-bit VM, and 1024k in the 64-bit VM. On x86 Solaris/Linux it is 320k in the 32-bit VM and 1024k in the 64-bit VM.
On Windows, the default thread stack
size is read from the binary
(java.exe). As of Java SE 6, this
value is 320k in the 32-bit VM and
1024k in the 64-bit VM.
You can reduce your stack size by
running with the -Xss option. For
example:
java -server -Xss64k
Note that on some versions of Windows,
the OS may round up thread stack sizes
using very coarse granularity. If the
requested size is less than the
default size by 1K or more, the stack
size is rounded up to the default;
otherwise, the stack size is rounded
up to a multiple of 1 MB.
