Hi, starting to write up some documentation for 3.4.0 has lead to (re-) reading various parts of the existing documentation. Regarding the issue in the subject. Would it be ok to include the corresponding fix in 3.4.0? It makes Maven 3.4.0 dependency management behave exactly as it is documented. Currently dependency management really is not transitive and is still kept compatible to Maven 2 (broken behaviour). Fix would be to replace ClassicDependencyManager [1] with TransitiveDependencyManaget [1]. This is one of things postponed a few months ago when the maven resolver was on its way. Now that it's there, I see no reason to not include that fix in 3.4.0. Why keep things still compatible to Maven 2 when that is EOL? WDYT?
[1] <https://git-wip-us.apache.org/repos/asf?p=maven-resolver.git;a=tree;f=maven-resolver-util/src/main/java/org/eclipse/aether/util/graph/manager;h=79506b8e925b5586c8065204997ead06245686bf;hb=HEAD> Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
