Figured it out. Because I haven't defined any themes (because it's a pure AS project) it's compiling in the default halo.swc via the mx.swc. Therefore I added mx.swc as an exclusion to the flex-framework dependency and it's now not compiling the halo.swc.
Interesting that this theme compiling behavior is added just by using the [Frame] metadata. On Mar 30, 6:02 pm, misterbenn <[email protected]> wrote: > I've got a pure Actionscript project where I am using the Frame > metadata tag to trigger a factory. I'm using this to trigger a factory > class to load RSLs - basically in a similar way to what Flex is doing. > Specifically I need to declare the [Frame] on a superclass of the main > application class (see my posthttp://www.dogcatfishdish.com/blog/?p=145) > to trigger the auto-generated IFlexModuleFactory > > When I've created a test project, it works fine, and the final swf > size is small (about 2k), i.e. it only brings in whats needed from the > Flex framework. > > When I bring this method into a flexmojos project, it compiles and > works fine, but the final swf size is massive - about 300k. A quick > look at the link report shows it's compiling in all the Flex > framework. > > I can't see anything in the flexmojos docs about sorting this out, and > can see anything obvious in flex-config either. > > I've had a play with using the frame parameter (https:// > repository.sonatype.org/content/sites/flexmojos-site/4.0-SNAPSHOT/ > compile-swf-mojo.html#frames) but with no luck, as I specifically need > to target a superclass of the main app to auto-generate the factory > subclass. > > Any clues, any suggestions? -- 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/
