I think you're right. The main issue here is c:1 is the first closest one,
but since the c:2 has compile scope, so should c:1. However, that doesn't
change the scope for transitive dependencies of c:1
A bit off-topic: Where is this scope order specified? In case of custom
scopes we probably need to do something with scope-order too.
Robert
On Fri, 15 Jul 2016 17:56:01 +0200, Christian Schulte <[email protected]>
wrote:
Hi,
I have a question regarding the description of MNG-4800. Why should the
scope of x be compile? The part "instead of ... x:compile". Is this
really correct? I see no reason why the scope of x should be updated to
compile. It should be kept runtime because it is a runtime dependency of
c no matter what scope of c is resolved. Can someone explain the reason
for this. Maybe based on a real example. I am asking because I think the
integration test maybe incorrect.
<https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=blob;f=core-it-suite/src/test/java/org/apache/maven/it/MavenITmng4800NearestWinsVsScopeWideningTest.java;h=9e163202b5aba9d977bce5a64b9557ff45c0ee67;hb=HEAD>
<https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=tree;f=core-it-suite/src/test/resources/mng-4800;h=d254e7dd63d7f99bc15ad0a1fca3e146b964f8b7;hb=HEAD>
Regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
