Am 12/28/16 um 22:21 schrieb Guillaume Boué: > > How come the tests compile fine with Maven 2.2.1, 3.0.5 and 3.3.9 then? >
I'd say this is the root cause of nearly all issues we are having a hard time fixing and shipping. It does not make sense to compare some recent behaviour to some former behaviour when that former behaviour is a result of patches trying to make things behave in a way users expect it. Using Maven 2.x or 3.x as the specification of how things /should/ behave when even the documentation says things really are meant to be different than what we ship is rediculous, IMHO. What we now have on master is consistent with itself and matches the documentation. That's how Maven 2.0.0 should have behaved from day one but did not. The documentation in this area has not been changed for more than nearly a decade. Maven never behaved that way. I am not kean on endless discussions about things. I do not have enough experience with GIT. Just create a branch of current master and then reset master to 3.3.9 so that I can squash and merge issues for the next release one by one into master and get master into a state it would pass a release vote. That's what I was refering to with "release branch". Passes a release build, passes all core and plugin ITs and passes a release vote. Master clearly does not pass a release vote. Hopefully what will pass a release vote is not just coloured output. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
