Hello, I have some rsl that I will call here sample-rsl2 and some another rsl called sample-rsl. sample-rsl has a dependency to sample-rsl2 and call a library from it. The dependency:tree of sample-rsl contains:
[INFO] br.com.p2d.ehr:sample-rsl:swc:0.1-SNAPSHOT [INFO] +- br.com.p2d.ehr:sample-rsl2:swc:0.1-SNAPSHOT:rsl I also have a project called sample-module that depends on sample-rsl. The tree contains: [INFO] br.com.p2d.ehr:sample-module:swf:0.1-SNAPSHOT [INFO] +- br.com.p2d.ehr:sample-rsl:swc:0.1-SNAPSHOT:rsl [INFO] | \- br.com.p2d.ehr:sample-rsl2:swc:0.1-SNAPSHOT:external (scope managed from runtime) What I want to know is if this is the expected behavior. Shouldn't the rsl scope be transitive? The module does not run for the same motive. It's not just a problem with the dependency:tree. Thanks, Rafael. -- 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/
