Yes, we are facing the same problems. Not sure whether this is a Maven problem, an Adobe compiler or a Flex mojos problem (personally I suspect the Adobe compiler, since IntelliJ has similar problems, when performing a build using the Adobe compilers), but there is a reason for sure, why Java compiles always fork a JVM for each compile process. Would be great if Flex mojos could also do that: Fork a JVM for each compile and exit that JVM after compliation thus making sure that all consumed resources are released.
-- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/
