Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
MIME-Version: 1.0
In-Reply-To: <b2362997-26af-6621-4b13-6be0d5896508@gmail.com>
References: <E24CE866-51A7-49BB-937F-4E3259FB453D@apache.org>
 <2e4263ab-d79c-e126-5664-d2ce91cc18a6@apache.org> <eab8610c-6c62-c870-9a80-8be4beac3992@gmail.com>
 <CACLE=7MUuaZTtzwuohsMpCr3yk9vBZd5D+F1bCHBkyLOXeCYcQ@mail.gmail.com> <b2362997-26af-6621-4b13-6be0d5896508@gmail.com>
From: Romain Manni-Bucau <rmannibucau@gmail.com>
Date: Fri, 11 Aug 2017 12:04:26 +0200
Message-ID: <CACLE=7OG5jzyhzuKX0nZSwDZ6d_18etcHgyY2e4zKGn5EukN+A@mail.gmail.com>
Subject: Re: CXF 3.2?
To: "dev@cxf.apache.org" <dev@cxf.apache.org>
Content-Type: multipart/alternative; boundary="f403045f280a623aba05567771b7"
archived-at: Fri, 11 Aug 2017 10:04:59 -0000

--f403045f280a623aba05567771b7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

2017-08-11 12:02 GMT+02:00 Sergey Beryozkin <sberyozkin@gmail.com>:

> Hi Romain
> On 11/08/17 06:41, Romain Manni-Bucau wrote:
>
>> @Sergey: java 8 or 9? - guess it was a 9 right? Anyway we - as asf - own=
 G
>> so if needed, dont hesitate to ping ;).
>>
>> Java 8 as far as I know, JAX-RS 2.1 is Java 8, I've checked the source,
> https://search.maven.org/#search%7Cga%7C1%7Cjavax.ws.rs
>
> module info is shipped, I recall it was done to make it loadable by Java
> 9, hmm, I do not see any Java 8 specific mechanism used RuntimeDelegate.
> So may that is just it, module info is shipped to help it loaded with
> Java9, and we will just need the regular spec bundle for OSGI...


Yep, that's what I had in mind so not a requirement for JAX-RS 2.1 by
itself :)


>
>
> Very happy to see 3.2 coming and Meecrowave would be interested to upgrad=
e
>> asap. Only "?" I have is if dependencies will not grow too much -
>> atmosphere for instance - but sure we can tackle it iteratively.
>>
>> SSE code is in a separate module so if you do not need it (or web socket
> transport) then no Atmosphere dep will be pulled in


Issue is when you need it (since it is in the spec I guess we can assume
you want it), not sure why we can't get a plain implementation for most of
the spec and just use atmosphere if present, would help to adopt it no?


>
>
> Sergey
>
>
> Le 11 ao=C3=BBt 2017 00:02, "Sergey Beryozkin" <sberyozkin@gmail.com> a =
=C3=A9crit :
>>
>> We can get it for 3.2.1 for ex, swagger-core + swagger-jaxrs which
>> interacts with the new swagger-core would need to be available, so it is=
 a
>> bit tight...
>>
>> Sergey
>>
>> On 10/08/17 20:37, Dennis Kieselhorst wrote:
>>
>> Good plan. I'd like to see support for Swagger/ OpenAPI Spec 3.0.0 in
>>> CXF 3.2 but we should postpone it if no updated swagger-core library is
>>> available by Sept 1st.
>>>
>>> Regards
>>> Dennis
>>>
>>>
>>>
>>

--f403045f280a623aba05567771b7--