Should there be a difference (dependency wise) for a swc dependency or an rsl dependency?
I can look at the dependency tree later tonight. On Nov 8, 2010 5:08 PM, "Marvin Froeder" <[email protected]> wrote: > This has nothing to do with flexmojos. Flexmojos doesn't resolve the > dependencies, maven does that. Flexmojos will respect whatever maven does. > > $ mvn dependency:tree > >> --- maven-dependency-plugin:2.1:tree (default-cli) @ >> flexmojos-unittest-flexunit4 --- >> org.sonatype.flexmojos:flexmojos-unittest-flexunit4:swc:4.0-SNAPSHOT >> +- >> org.sonatype.flexmojos:flexmojos-unittest-support:swc:4.0-SNAPSHOT:external >> +- com.adobe.flexunit:flexunit:swc:4.0-beta-2:external >> +- com.adobe.flex.framework:airglobal:swc:4.5.0.17855:provided >> +- com.adobe.flex.framework:airframework:swc:4.5.0.17855:external >> +- com.adobe.flex.framework:framework:swc:4.5.0.17855:external >> +- com.adobe.flex.framework:mx:swc:4.5.0.17855:external >> +- com.adobe.flex.framework:framework:rb.swc:4.5.0.17855:compile >> \- com.adobe.flex.framework:mx:rb.swc:4.5.0.17855:compile >> > > So, should match whatever maven output, the only exception is for > airglobal/playerglobal that will be external no mater the scope you define > (this is a flex thing) and the compile scope... that will be translated into > external for SWC projects and into merged for SWF projects. Valid scopes > are empty (compile), external, internal, merged, rsl, caching and test. > > Check the dependency:tree, if flexmojos doesn't match to it, then we have a > FM bug, otherwise it is a maven thing. > > Send you dependency:tree > > > VELO > > > On Mon, Nov 8, 2010 at 9:24 PM, Ryan Gardner <[email protected]> wrote: > >> 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]<flex-mojos%[email protected]> <flex-mojos%[email protected]<flex-mojos%[email protected]> > >> For more options, visit this group at >> http://groups.google.com/group/flex-mojos >> >> http://flexmojos.sonatype.org/ >> > > -- > 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]<flex-mojos%[email protected]> > For more options, visit this group at > http://groups.google.com/group/flex-mojos > > http://flexmojos.sonatype.org/ -- 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/
