Re: [VOTE] Apache CXF 3.0.15 and 3.1.13 patch releases...

+1. Colm. On Thu, Sep 7, 2017 at 11:41 AM, Dennis Kieselhorst wrote: > +1 (non-binding) > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

Re: [VOTE] Apache CXF 3.2.0

+1. Colm. On Thu, Sep 7, 2017 at 9:59 AM, Sergey Beryozkin wrote: > +1 > > Thanks, Sergey > > > On 06/09/17 19:14, Daniel Kulp wrote: > >> It’s been 2 years since the last major CXF release.We have well over >> 100 JIRA’s of new features and enhancements that are only

Re: [VOTE] Apache CXF 3.0.15 and 3.1.13 patch releases...

+1 (non-binding)

[GitHub] cxf issue #309: [CXF-7491] Fork Stax & XSLT interceptors to make them Charse...

Github user sberyozkin commented on the issue: https://github.com/apache/cxf/pull/309 I'm not sure if users actually have ever tried to extend these classes, we can ask at the CXF users for example if someone has tried it...Can you please try to do another PR but based on updating

Re: [DISCUSS] Status of 3.0.x...

Indeed, good plan... Sergey On 06/09/17 20:14, Andriy Redko wrote: I think that keeping 3.2.x on master would make sense, at least till 3.2.1. As Dennis pointed out, with Java 9 just a few weeks away we may branch off 3.2 later and work on 3.3 (master) to make it good Jigsaw citizen.

Re: [VOTE] Apache CXF 3.2.0

+1 Thanks, Sergey On 06/09/17 19:14, Daniel Kulp wrote: It’s been 2 years since the last major CXF release.We have well over 100 JIRA’s of new features and enhancements that are only targeted toward 3.2. Let’s get it out! Staging repo:

Re: [DISCUSS] Status of 3.0.x...

+1 as well to dropping 3.0.x, and keeping master on 3.2.x for a while. Colm. On Wed, Sep 6, 2017 at 11:18 PM, Andy McCright wrote: > +1 to keeping 3.2 on master until 3.2.1. I also agree with declaring end > of support for 3.0.X (barring security vulnerabilities).