On Mon, Jan 2, 2017 at 1:38 PM, Hervé BOUTEMY <herve.bout...@free.fr> wrote:
> Christian, > > Please read Tibor's concerns: > - big change, > - near release (with parallel branches for JUnit 5) > And I'll add: noise, like addition of final, reordering of imports, > addition/ > suppression of empty lines > > Please follow Tibor's request, which tries to be as kind as possible: > > So now please revert last change [1] and let's start from the ground. > > We should again learn from the beginning and start communicating in the > > community; otherwise this is the end of the project. > In my uninteresting opinion, Tibor should formally veto the commit. That's not un-nice, it's the way to express, clearly and crisply, his view that the change is not acceptable without further discussion and refinement. On the other hand, I don't think that the remarks about 'playgrounds' or 'sandboxes' are appropriate or respectful. We should all assume good intent and professional intent. We are running a CTR system here, and so we should expect something like this to happen from time to time, where someone commits with the best of intentions and someone else feels strongly that more work is needed. Once Tibor has vetoed, Christian should revert, and then the process should unfold from there. > Regards, > > Hervé > > Le lundi 2 janvier 2017, 18:46:00 CET Christian Schulte a écrit : > > I am not checking out surefire because I am bored. I get blamed for > > failing ITs and I am quite pissed that the CI system is sending out > > failure notifications and all you see is an issue with surefire and not > > with the build job or the actual build you get an email for. With > > current master, there are no IT failures (core and plugins) and > > everything can be build as well. Jenkins has not send out a single > > success mail although it could do that for a long time already. I > > re-started the build jobs multiple times a day and they never run > > through. It's not Jenkins to blame or anything about the CI system. Most > > of the time it's surefire. There is one core IT failing sporadically on > > Windows which seems to have to do with some core extension classpath > > ordering issue. I don't know. No-one seems to care about that. It could > > have been introduced by the changes to add support for extension.xml > > files. Nothing I have worked on. The core has been released with that IT > > failing. > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >