Am 12/28/16 um 22:50 schrieb Robert Scholte: > "That's always been that way." > Well, apparently not. Maybe it was documented that way, but I expect that > users did their dependency management which felt natural and which worked.
I created an issue in JIRA to track this: <https://issues.apache.org/jira/browse/MNG-6141> It has an example project attached demonstrating what is going on using versions and not scopes or the optional flag. I think that's the real issue at hand. It just happens that managing something transitive to something non-transitive starts to work correctly in Maven 3.4+ and this produces compilation errors in Wagon. No-one is noticing those dependency management overrides are only in effect locally during building the module declaring them an nowhere else. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
