Recently, some users have reported that their application has been stuck in the GroovyCompile task. It looks like that was due to default lower jvmArgs setting i.e. 512M. We have updated the base profile to configure minimum -Xmx1024M and one can configure it to a lower value based on their application.
Recently, some users have reported that their application has been stuck in the GroovyCompile task. It looks like that was due to default lower jvmArgs setting i.e. 512M. We have updated the base profile to configure minimum
-Xmx1024Mand one can configure it to a lower value based on their application.