> On Nov 23, 2018, at 3:52 PM, César Hernández Mendoza <cesargu...@gmail.com> > wrote: > > Hi everybody, > > I did a git bisect and this is the final output: > > a5513230e8f77a4985916f901c3eda2c5c45c6d2 is the first bad commit > commit a5513230e8f77a4985916f901c3eda2c5c45c6d2 > Author: Dennis Kieselhorst <d...@apache.org> > Date: Tue Oct 30 15:30:06 2018 +0100 > > Update CXF to latest release > > :100644 100644 42b6643b26a64db3e381159191d588102e80478e > 732703824b1d27f5c12f3ac6669c0c5a59a63030 M pom.xml > > > Notice that my intention is not to blame anyone, instead, I'm providing > enough context that allows all of us to help in fixing this issue. > I would highly appreciate any information you may have about the background > of this commit [1],
I have a saying: The only people who don't break the build are those who do nothing. :) On background, I think it's not more complicated than trying to stay current. > Action for next week: [..] > b) It's important also to notice that we definitely need to add to TomEE > some tests related to MicroProfile rest client integration. You hit the nail on the head here. If examples are finding bugs, it's a sign we need more tests of our own. Mind you, the act of creating examples has an amazing way of surfacing bugs, just when they do, we should add a test case so the example isn't the only thing keeping us safe. -David
