Am 12/19/16 um 15:56 schrieb Michael Osipov: > [DEBUG] net.sf.michael-o.dirctxsrc:dircontextsource:jar:1.3:compile > [DEBUG] org.slf4j:slf4j-simple:jar:1.7.21:runtime (scope managed from > test by com.company.project:project-parent:0.11-SNAPSHOT)
<https://issues.apache.org/jira/browse/MRESOLVER-9> That's what the resolver does. It uses the management as a global override for transitive dependencies. It's correct this will get managed to 'runtime'. That's what you have in your management. > My questions are: > 1. Is this another fix in master where I relied on an erratic behavior in > core previously? > 2. Should depMgmthave influence on transitive deps or direct only? Direct dependencies (those being declared in the POM) are handled by the core (model builder), transitive dependencies are handled by the resolver. It has always been that way. This is what has changed: <https://git-wip-us.apache.org/repos/asf?p=maven-resolver.git;a=blobdiff;f=aether-impl/src/main/java/org/eclipse/aether/internal/impl/DefaultDependencyCollector.java;h=62a8ff2a0ab8fd99576777446266ca588bc0fe40;hp=f1fcbf258de04b698e0ce23ca91e6827b5e6a47d;hb=1ee92862c67ec98564c4d8be1207355960f1dd5d;hpb=11a061b66fd15b8c3584f48afa69955d9392861e> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
