On Mon, Jun 7, 2010 at 5:27 AM, Matt C <[email protected]> wrote: > However: > 1 - I don't want to have to specify the directory location of the > MXMLC.EXE binary > 2 - would much prefer to use the same compiler as all the other code > uses (ie, whatever FlexMojos uses).
Adobe provides what they call the Flex OEM compiler API. It's a way to call the Flex compiler through a Java interface. It ends up calling the same code as mxmlc.exe does, but the configuration setup is just a little different. That's what Flexmojos 3 uses. But they haven't maintained it well, so I think Velo is considering calling the compiler directly (or maybe already has in FM4). There is a way to pass maven dependencies to antrun, but I've only read about it, never used it. To use the same compiler, you would need to figure out the right settings for the Flex OEM compiler and pass that in, plus get the classpath for the OEM compiler right. I don't think that's totally straightforward, though probably can be done. Logan -- 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/
