Make sense, thanks Dennis. We figured out that the upgrade to latest 2.0.x was
also problematic, right? Postponing it to 3.3.x would be better (imho). Colm,
what do you think?
Best Regards,
Andriy Redko
DK> Hi,
DK> we already noticed this in February:
DK>
https://lists.apache.org/thread.html/e440d7e162f4462972a6116cc523c78b3f1b9128ca23a2fcf9d55167@<dev.cxf.apache.org>
DK> Failing tests are part of the discussion.
DK> I think we should postpone a breaking change until 3.3.x.
DK> Regards
DK> Dennis
