Hey Dennis,
I think we still on JAXB 2.2.x on master:
<cxf.jaxb.version>2.2.11</cxf.jaxb.version>
Let us try to upgrade to 2.3.0? :-)
Thanks.
Best Regards,
Andriy Redko
DK> Now that we have 3.3.x in master we should be able to upgrade it. Has
anyone already started with this?
DK> Cheers
DK> Dennis
DK> On 2018/04/19 09:28:29, Colm O hEigeartaigh <cohei...@apache.org> wrote:
>> Let's wait for Dan's opinion on this - maybe the upgrade is more suitable
>> for a new major release instead of 3.2.x?
>> Colm.
>> On Thu, Apr 19, 2018 at 10:11 AM, Francesco Chicchiriccò <
>> ilgro...@apache.org> wrote:
>> > On 18/04/2018 13:02, Andriy Redko wrote:
>> >
>> >> Hi Francesco,
>> >>
>> >> Could you please try to upgrade to JAXB 2.3.0 and run the tests to see
>> >> what breaks? Keeping
>> >> the dependencies up to date is always a good thing :) Thanks.
>> >>
>> >
>> > Hi Andriy,
>> > I cannot agree more, about keeping dependencies up to date.
>> >
>> > Unfortunately, it's not easy for me to identify how to upgrade to JAXB
>> > 3.0: maybe some OSGi guy around can do this?
>> > Then, upgrading swagger-jaxrs2 is trivial.
>> >
>> > Regards.
>> >
>> > FC> Hi all,
>> >> FC> I just reverted the upgrade to swagger-jaxrs2 2.0.1 [1] since, as
>> >> FC> reported by Colm via IRC, that breaks osgi/karaf/features: it looks
>> >> like
>> >> FC> swagger-jaxrs2 2.0.1 has a dependency on JAXB 2.3.0, whereas CXF still
>> >> FC> uses 2.2.x.
>> >>
>> >> FC> Is it possible to upgrade to JAXB 2.3.0?
>> >>
>> >> FC> Regards.
>> >>
>> >> FC> [1]
>> >> FC> https://github.com/apache/cxf/commit/96cf54c8577abb504113065
>> >> c7c8f4e3d86b84bf9
>> >>
