I saw an earlier thread on this, but I think it predated FM4 so maybe some of the technical issues have changed.
Say I have a project set up like this: foo-common-lib - depends upon 3rd-party-pretty-graphics-lib - depends upon 3rd-party-something-lib and foo-app1 and foo-app2 that both depend upon flex-common-lib If I set up the apps to link to foo-common-lib as just a normal swc, it works fine and the stuff that gets used gets merged in, and the transitive dependencies are included in the main app project If, however, I set up the apps to link to the foo-common-lib as an RSL... then the build breaks because the compiler can't find the 3rd-party-pretty-graphics-lib stuff anymore. I tried to be tricky and add in two dependencies to foo-common-lib, one in scope <compile> and one as scope <rsl> but it didn't work :( Is there any way to get RSLs transitive dependencies to "just work" the way an experienced maven user would expect them to? Ryan -- 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/
