Maybe I am just leading myself into a dead end here... With FlexMojos 4 calls Mxmlc.mxmlc(String[] args) which intern calls CompilerAPI.usePathResolver() which sets up a new PathResolver on ThreadLocalToolkit.
The way FlexMojos 3 worked it was able to set PathResolvers on the Application class which is how the property "enableMavenResourcesResolver" seemed to work. With FlexMojos 4 the only thing I can imaging doing is call ThreadLocalToolkit and set this but it will be cleared out by CompilerAPI.userPathResolver() :@ Unless there is some other way I don't think we can add additional PathResolvers to the OEM compiler from FlexMojos 4. If there are any thoughts on this I am willing to investigate more but right now there doesn't seem to be an easy solution. Lance -- 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/
