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
> 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)
>
>
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)
Hi Michael,
I can reproduce that behaviour as well. In the current 3.4.0, a
dependency management that declares a dependency with scope runtime will
manage a transitive dependency of scope test. A reproducer is
org.slf4j
slf4j-simple
1.7.21
Hi folks,
I just tried a fresh Maven master (7d1d8ac0c14bdea6c92356436bfc6f8548cbae8b;
2016-12-19T15:22:22+01:00)
on an in-house project.
My project's parent POM states in depMgmt:
org.slf4j
slf4j-api
${slf4j.version}
org.slf4j
jcl-over-slf4j
${slf4j.version}
runtime
