Thanks César.
Will Review.
Bruno Baptista
https://twitter.com/brunobat_
On 17/12/18 16:09, César Hernández Mendoza wrote:
Hi Bruno,
I saw your message on the PR.
Conflict is now fixed :)!
El vie., 14 dic. 2018 a las 22:34, César Hernández Mendoza (<
cesargu...@gmail.com>) escribió:
Hi,
Since now the current master is using mp rest client 1.1,
https://issues.apache.org/jira/browse/TOMEE-2298 is no longer blocking
TOMEE-2297.
I updated and fixed the PR, now is ready for review:
https://github.com/apache/tomee/pull/210
Ticket: https://issues.apache.org/jira/browse/TOMEE-2297
El mié., 28 nov. 2018 a las 13:20, César Hernández Mendoza (<
cesargu...@gmail.com>) escribió:
Hi,
Today I confirmed with Any McCrigth, from CXF project, that this is a bug
in cxf 3.2.7.
I opened https://issues.apache.org/jira/browse/CXF-7912 and he will work
on the fix that I already tested locally building cxf 3.2.8 snapshot.
I updated my PR [1] with the TomEE jira [2] reference in the
title+commit meesage and also created a ticket to update cxf to 3.2.8[3]
when the release becomes available.
[1] https://github.com/apache/tomee/pull/210
[2] https://issues.apache.org/jira/browse/TOMEE-2297
[3] https://issues.apache.org/jira/browse/TOMEE-2298
El mar., 27 nov. 2018 a las 21:32, César Hernández Mendoza (<
cesargu...@gmail.com>) escribió:
Hi,
Quick update on this issue:
I found the commits [1] on cxf 3.2.x-fixes branch that added this
behavior in the <cxf.version>3.2.7</cxf.version>.
Understanding the version dependency between TomEE, MicroProfile,
MicroProfile Rest Client and CXF is kind of tricky.
I'm building also a matrix to simplify future troubleshooting to know
this 4 dependency chain.
Tomorrow I'm going to continue troubleshooting this issue and check if
we can fix it with the update Roberto [2] already identified and/or if
cxf 3.2.7 broke backward compatibility with 3.2.6 for the MP rest client
since the TCK for MP Rest client doesn't cover the scenario added in
cxf 3.2.7.
[1] https://issues.apache.org/jira/browse/CXF-7868
[2] https://issues.apache.org/jira/browse/TOMEE-2282
El vie., 23 nov. 2018 a las 22:32, David Blevins (<
david.blev...@gmail.com>) escribió:
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
--
Atentamente:
César Hernández Mendoza.
--
Atentamente:
César Hernández Mendoza.
--
Atentamente:
César Hernández Mendoza.
