Upgraded to IJ 12.0.3 this morning and found that it runs OOM during maven builds and will not complete a JBoss deploy/run. Rolling back to 12.0.2 fixes the issues, anyone else encountering this or have some insight as to what is going on? Tried upping memory allocation to maven, IJ and JVM in turn, spent the better part of a day on this will little success on our end.
For now, we've rolled back to 12.0.2 until IJ is stable with Maven again.
Can you try to start IJ with -XX:+HeapDumpOnOutOfMemoryError setting enabled (auto-generate heap dump on OME) and submit a dump to ftp://ftp.intellij.net/.uploads/?
Thanks for the quick response Denis - I wasn't sure where to set that parameter so after some searching stumbled on the .vmoptions files in the bin/ folder. Just to test, made some changes in there and maven appears to be building fine now. Just need to resolve why spring is failing to resolve some deps with 12.0.3 and we're home free .
My settings are now like so: http://screencast.com/t/qksfsGprt7
Ok, so we've go about as far as we can, now theres a real issue in 12.0.3 with our dependencies and we're not certain what i going on yet, heres a stack trace from what we are seeing: http://pastie.org/6067715
What is odd here, is that if I start up 12.0.2 and use the exact same project, settings, etc... (afaik), it runs fine, but in 12.0.3 it does not.
Looks like there is something wrong in your code that causes an exception in GWT compiler:
portable entity fx.lifescape.shared.data.PatientContext contains a field (primaryPatientDO) that is not known to the marshaller:
I don't know why this error isn't shown in IDEA 12.0.2, may be it uses a different version of some library.
"Develop with pleasure!"