I have a question regarding how maven handles transitive dependencies for Flex applications. Lets say I have:
component1.swc (built optimized so available as swc & rsl) component1 depends on (helper1.swc & helper2.swc) The scope of these is set to External to keep the final app size smallest. component2.swc (built optimized so available as swc & rsl) component2 depends on (helper1.swc & helper3.swc) The scope of these is set to External to keep the final app size smallest. app.swf depends on component1 (dependency scope is set to RSL) depends on component2 (dependency scope is set to RSL) Now my question is how does app.swf know there are transitive dependencies (helper1, helper2 & helper3) that must be included? In Java maven would figure this out and all these would be added to the classpath without any configuration in app.swf's pom.xml. How does this work with Flex? Ideally we want helper1 as rsl because it was used twice. Ideally helper2 & helper3 would be rsl too but could be merged as there is only one use of each anyway. Another approach: If maven does not help with flex transitive dependencies are we better off not using RSLs at all (for our components). If we were to always use merged or internal scope for all our swc generation, when these are included in the final swf is there a way (perhaps this is standard behavior) to optimize the linkage here so that only one class definition is included? I.e. If all our swc(s) included all their dependencies when the swf is made can the linker optimize such that the swf is similar in size to the sum of rsls + swf? -Dave -- 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?hl=en?hl=en http://blog.flex-mojos.info/
