-1 No one has likely to have read the information and you’re reasoning is illogical. Repeatedly you seem not to care if you’re going to break a users build because of lack of adherence to what you think is right.
What’s “right” is the way it currently works within this minor version. > On Nov 14, 2016, at 4:01 PM, Christian Schulte <c...@schulte.it> wrote: > > 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 > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Takari and Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io --------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
