Excluding definitions is pretty straightforward. If a definition is in the SWC you are “extern-ing” then those definitions don’t go in the output module. And then you are obligated to provide those definitions somehow in some parent ApplicationDomain.
I’ve blogged about shared modules that get loaded directly into the main application domain so multiple modules can share those definitions. RSLs also bring in shared definitions. You can unzip a swc and check its catalog.xml to see what definitions are in a swc. HTH, -Alex On 9/24/15, 3:58 AM, "Davori" <don.fasa...@gmail.com> wrote: >Thanks Alex I've considered those 9keepAllTypeSelectors and , > >This appears to be that defintions within Assets.swf of airframework.swc >is >what is missing from my modules and causing these errors the app domain of >my modules is a child domain. I noticed that including the mx theme in my >compilation resolved this error in the main module I had a problem with >but >not in all my modules. > >I also think it could be to do with transitive dependencies. I'm not sure >how those work with load externs in the case that I have of two swcs one >*core *one that's a dependency for another *client *swc and the core one >is >also a direct dependency for the module, I then set the module to exclude >both swcs from it's definitions, could that be why it's being stripped >out? > > >Regards, > >Lyndon > > > >-- >View this message in context: >http://apache-flex-users.2333346.n4.nabble.com/Flexmojos-with-Debug-true-i >n-module-ensures-styles-are-embedded-but-debug-false-does-not-tp11167p1122 >3.html >Sent from the Apache Flex Users mailing list archive at Nabble.com.
