Well if it's fork=no you use the VM of the Build therefore you provide the VM 
args to Ant, if you have fork=yes, it creates a dedicated VM for the 
compilation and you have to manually pass in arguments to the creation of that 
VM ...

... you could also try the Maven build ;-)


Von: Justin Mclean <jus...@classsoftware.com>
Gesendet: Montag, 19. September 2016 23:19:01
An: dev@flex.apache.org
Betreff: Re: mxmlc error null with "large" project


I do have a vague memory that it picks up the memory argument in different 
spots depending if you have fork=“yes” or fork=“no”.


Reply via email to