Am 12/20/16 um 10:28 schrieb Michael Osipov: >> 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. > > I am horribly afraid that you are right, our documentation says: > "b is defined in B's parent's dependency management section and since > dependency management > takes precedence over dependency mediation for transitive dependencies, > version > 1.0 will be selected should it be referenced in a or c's pom. b will also > have compile scope." >
Looking at my personal POMs, I really never manage any scopes. This may be due to Netbeans providing hints whenever you override something from management. There is not a single multi-module project here where the scope from the management would not have to be overridden in at least one module of the reactor. I am not sure the core model builder really is doing the right thing. If it would manage (override) things the same way the resolver does, things like this would not happen. Your 'test' dependency would always have been 'runtime', no matter what. That would have made you remove the scope from management because the scope is not the same across all modules of that reactor. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
