You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Sergey Beryozkin <sb...@gmail.com> on 2015/02/13 18:20:32 UTC
Planning for Java8 trunk
Hi All,
We've had a brief chat with Dan earlier about the possibility of
introducing a Java 8 trunk after it was announced JAX-RS 2.1 API would
be Java 8 based.
I'd like to justify here why IMHO this would be a very good thing for CXF:
- Java 8 is recognized to have a lot of new language features that can
help with significantly enhancing the capabilities of a given project.
Functional programming, security related enhancements, etc, etc. IMHO
opening a Java 8 trunk would help us 're-invigorate' the CXF source (all
frontends) with respect to the asynchronous, security-related and other
processing and will likely lead to the introduction of the new features
we can not even think of now. It will also excite the CXF community at
large.
- JAX-RS 2.1 requires Java8. JAX-RS 2.1 started its work in December
2014 and I do expect Jersey and RestEasy teams publishing the snapshots
more or less in sync with the ongoing API updates. Many users do want to
play with the latest and greatest API asap. Besides, implementing
iteratively would make it easier for us to deal with the other
commitments we may have.
We have 3.1.0 and 3.0.x but there are no major differences between them
from a feature point of view except that 3.1.0 is Java 7 based (with
some related improvements).
So I believe it would be good to have a Java 8 trunk. The major question
is when. But I hope it can be opened by the end of this year or possibly
even a bit earlier.
IMHO the following may make sense:
Open it in the end of life for 2.7.x and either 3.1.0 or 3.1.1 releases.
2.7.x is nearly 2.7.15 now and I guess there will be 3 or so 2.7.x
releases afterwards max.
If 2.7.x can be 'closed' and '3.1.0' released at the same time then IMHO
it can just make sense to branch 3.1.x at that point and open a Java 8
CXF 4.0 trunk. Otherwise do it after 2.7.x is closed and 3.1.1 is released.
Thoughts are welcome
Thanks, Sergey
Re: Planning for Java8 trunk
Posted by Jim Ma <ma...@gmail.com>.
Is there any plan to create java8 trunk? java7 is already EOL for couple
of month. Do we still have blockers to move to support java8 ?
Cheers,
jim
On Mon, Feb 16, 2015 at 9:22 PM, Jason Pell <ja...@pellcorp.com> wrote:
> Seems reasonable.
> On 16/02/2015 9:15 PM, "Aki Yoshida" <el...@gmail.com> wrote:
>
> > I just checked the release dates of the last 2.4.x, 2.5.x and 2.6.x
> > versions.
> > Closed 2.4.10 05-Oct-2012
> > Closed 2.5.11 16-Jul-2013
> > Closed 2.6.16 07-Oct-2014
> >
> > So I think it is reasonable to expect 2.7.x to be closed sometime
> > later this year, that means to have only a few more releases on 2.7.x.
> >
> > Maybe we can already mention in the 2.7.15 release note that there
> > will be only a few more releases planned (2~3).
> >
> >
> > 2015-02-15 23:15 GMT+01:00 Jason Pell <ja...@pellcorp.com>:
> > > Java 8 support I think is paramount for moving project forward. I just
> > > don't want the death of 2.7 to be a prerequisite :-)
> > >
> > > Its probably going to be at least 6 months before I can migrate my own
> > > project to 3.x
> > > On 16/02/2015 6:03 AM, "Sergey Beryozkin" <sb...@gmail.com>
> wrote:
> > >
> > >> Sure. I guess it would be wise to discuss the introduction of
> > >> a Java 8 trunk without making 2.7.x and 3.0.x and 3.1.x releases as
> the
> > >> prerequisites.
> > >> At some point we did have 4 branches (including a trunk). Ultimately,
> > >> IMHO, a Java 8 trunk can indeed help with getting more new features
> into
> > >> CXF. Java 7 reaches the end of life in two months. I agree things are
> > >> changing at a much slower rate in the productions. But starting
> planning
> > >> for a Java 8 trunk is better be done earlier than later :-)
> > >>
> > >> Sergey
> > >>
> > >>
> > >> On 13/02/15 22:32, Jason Pell wrote:
> > >>
> > >>> By customers I don't mean my companies customers, I mean users of cxf
> > 2.7
> > >>>
> > >>> On Sat, Feb 14, 2015 at 9:30 AM, Jason Pell <ja...@pellcorp.com>
> > wrote:
> > >>>
> > >>> From a purely selfish point of view, I hope that 2.7 end of life is
> > >>>> announced well in advance, as a lot of customers will have to
> migrate
> > to
> > >>>> 3.x.
> > >>>>
> > >>>> On Sat, Feb 14, 2015 at 4:20 AM, Sergey Beryozkin <
> > sberyozkin@gmail.com>
> > >>>> wrote:
> > >>>>
> > >>>> Hi All,
> > >>>>>
> > >>>>> We've had a brief chat with Dan earlier about the possibility of
> > >>>>> introducing a Java 8 trunk after it was announced JAX-RS 2.1 API
> > would
> > >>>>> be
> > >>>>> Java 8 based.
> > >>>>>
> > >>>>> I'd like to justify here why IMHO this would be a very good thing
> for
> > >>>>> CXF:
> > >>>>>
> > >>>>> - Java 8 is recognized to have a lot of new language features that
> > can
> > >>>>> help with significantly enhancing the capabilities of a given
> > project.
> > >>>>> Functional programming, security related enhancements, etc, etc.
> IMHO
> > >>>>> opening a Java 8 trunk would help us 're-invigorate' the CXF source
> > (all
> > >>>>> frontends) with respect to the asynchronous, security-related and
> > other
> > >>>>> processing and will likely lead to the introduction of the new
> > features
> > >>>>> we
> > >>>>> can not even think of now. It will also excite the CXF community at
> > >>>>> large.
> > >>>>>
> > >>>>> - JAX-RS 2.1 requires Java8. JAX-RS 2.1 started its work in
> December
> > >>>>> 2014
> > >>>>> and I do expect Jersey and RestEasy teams publishing the snapshots
> > more
> > >>>>> or
> > >>>>> less in sync with the ongoing API updates. Many users do want to
> play
> > >>>>> with
> > >>>>> the latest and greatest API asap. Besides, implementing iteratively
> > >>>>> would
> > >>>>> make it easier for us to deal with the other commitments we may
> have.
> > >>>>>
> > >>>>> We have 3.1.0 and 3.0.x but there are no major differences between
> > them
> > >>>>> from a feature point of view except that 3.1.0 is Java 7 based
> (with
> > >>>>> some
> > >>>>> related improvements).
> > >>>>>
> > >>>>> So I believe it would be good to have a Java 8 trunk. The major
> > question
> > >>>>> is when. But I hope it can be opened by the end of this year or
> > possibly
> > >>>>> even a bit earlier.
> > >>>>>
> > >>>>> IMHO the following may make sense:
> > >>>>>
> > >>>>> Open it in the end of life for 2.7.x and either 3.1.0 or 3.1.1
> > releases.
> > >>>>>
> > >>>>> 2.7.x is nearly 2.7.15 now and I guess there will be 3 or so 2.7.x
> > >>>>> releases afterwards max.
> > >>>>>
> > >>>>> If 2.7.x can be 'closed' and '3.1.0' released at the same time then
> > IMHO
> > >>>>> it can just make sense to branch 3.1.x at that point and open a
> Java
> > 8
> > >>>>> CXF
> > >>>>> 4.0 trunk. Otherwise do it after 2.7.x is closed and 3.1.1 is
> > released.
> > >>>>>
> > >>>>> Thoughts are welcome
> > >>>>> Thanks, Sergey
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
>
Re: Planning for Java8 trunk
Posted by Jason Pell <ja...@pellcorp.com>.
Seems reasonable.
On 16/02/2015 9:15 PM, "Aki Yoshida" <el...@gmail.com> wrote:
> I just checked the release dates of the last 2.4.x, 2.5.x and 2.6.x
> versions.
> Closed 2.4.10 05-Oct-2012
> Closed 2.5.11 16-Jul-2013
> Closed 2.6.16 07-Oct-2014
>
> So I think it is reasonable to expect 2.7.x to be closed sometime
> later this year, that means to have only a few more releases on 2.7.x.
>
> Maybe we can already mention in the 2.7.15 release note that there
> will be only a few more releases planned (2~3).
>
>
> 2015-02-15 23:15 GMT+01:00 Jason Pell <ja...@pellcorp.com>:
> > Java 8 support I think is paramount for moving project forward. I just
> > don't want the death of 2.7 to be a prerequisite :-)
> >
> > Its probably going to be at least 6 months before I can migrate my own
> > project to 3.x
> > On 16/02/2015 6:03 AM, "Sergey Beryozkin" <sb...@gmail.com> wrote:
> >
> >> Sure. I guess it would be wise to discuss the introduction of
> >> a Java 8 trunk without making 2.7.x and 3.0.x and 3.1.x releases as the
> >> prerequisites.
> >> At some point we did have 4 branches (including a trunk). Ultimately,
> >> IMHO, a Java 8 trunk can indeed help with getting more new features into
> >> CXF. Java 7 reaches the end of life in two months. I agree things are
> >> changing at a much slower rate in the productions. But starting planning
> >> for a Java 8 trunk is better be done earlier than later :-)
> >>
> >> Sergey
> >>
> >>
> >> On 13/02/15 22:32, Jason Pell wrote:
> >>
> >>> By customers I don't mean my companies customers, I mean users of cxf
> 2.7
> >>>
> >>> On Sat, Feb 14, 2015 at 9:30 AM, Jason Pell <ja...@pellcorp.com>
> wrote:
> >>>
> >>> From a purely selfish point of view, I hope that 2.7 end of life is
> >>>> announced well in advance, as a lot of customers will have to migrate
> to
> >>>> 3.x.
> >>>>
> >>>> On Sat, Feb 14, 2015 at 4:20 AM, Sergey Beryozkin <
> sberyozkin@gmail.com>
> >>>> wrote:
> >>>>
> >>>> Hi All,
> >>>>>
> >>>>> We've had a brief chat with Dan earlier about the possibility of
> >>>>> introducing a Java 8 trunk after it was announced JAX-RS 2.1 API
> would
> >>>>> be
> >>>>> Java 8 based.
> >>>>>
> >>>>> I'd like to justify here why IMHO this would be a very good thing for
> >>>>> CXF:
> >>>>>
> >>>>> - Java 8 is recognized to have a lot of new language features that
> can
> >>>>> help with significantly enhancing the capabilities of a given
> project.
> >>>>> Functional programming, security related enhancements, etc, etc. IMHO
> >>>>> opening a Java 8 trunk would help us 're-invigorate' the CXF source
> (all
> >>>>> frontends) with respect to the asynchronous, security-related and
> other
> >>>>> processing and will likely lead to the introduction of the new
> features
> >>>>> we
> >>>>> can not even think of now. It will also excite the CXF community at
> >>>>> large.
> >>>>>
> >>>>> - JAX-RS 2.1 requires Java8. JAX-RS 2.1 started its work in December
> >>>>> 2014
> >>>>> and I do expect Jersey and RestEasy teams publishing the snapshots
> more
> >>>>> or
> >>>>> less in sync with the ongoing API updates. Many users do want to play
> >>>>> with
> >>>>> the latest and greatest API asap. Besides, implementing iteratively
> >>>>> would
> >>>>> make it easier for us to deal with the other commitments we may have.
> >>>>>
> >>>>> We have 3.1.0 and 3.0.x but there are no major differences between
> them
> >>>>> from a feature point of view except that 3.1.0 is Java 7 based (with
> >>>>> some
> >>>>> related improvements).
> >>>>>
> >>>>> So I believe it would be good to have a Java 8 trunk. The major
> question
> >>>>> is when. But I hope it can be opened by the end of this year or
> possibly
> >>>>> even a bit earlier.
> >>>>>
> >>>>> IMHO the following may make sense:
> >>>>>
> >>>>> Open it in the end of life for 2.7.x and either 3.1.0 or 3.1.1
> releases.
> >>>>>
> >>>>> 2.7.x is nearly 2.7.15 now and I guess there will be 3 or so 2.7.x
> >>>>> releases afterwards max.
> >>>>>
> >>>>> If 2.7.x can be 'closed' and '3.1.0' released at the same time then
> IMHO
> >>>>> it can just make sense to branch 3.1.x at that point and open a Java
> 8
> >>>>> CXF
> >>>>> 4.0 trunk. Otherwise do it after 2.7.x is closed and 3.1.1 is
> released.
> >>>>>
> >>>>> Thoughts are welcome
> >>>>> Thanks, Sergey
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
>
Re: Planning for Java8 trunk
Posted by Aki Yoshida <el...@gmail.com>.
I just checked the release dates of the last 2.4.x, 2.5.x and 2.6.x versions.
Closed 2.4.10 05-Oct-2012
Closed 2.5.11 16-Jul-2013
Closed 2.6.16 07-Oct-2014
So I think it is reasonable to expect 2.7.x to be closed sometime
later this year, that means to have only a few more releases on 2.7.x.
Maybe we can already mention in the 2.7.15 release note that there
will be only a few more releases planned (2~3).
2015-02-15 23:15 GMT+01:00 Jason Pell <ja...@pellcorp.com>:
> Java 8 support I think is paramount for moving project forward. I just
> don't want the death of 2.7 to be a prerequisite :-)
>
> Its probably going to be at least 6 months before I can migrate my own
> project to 3.x
> On 16/02/2015 6:03 AM, "Sergey Beryozkin" <sb...@gmail.com> wrote:
>
>> Sure. I guess it would be wise to discuss the introduction of
>> a Java 8 trunk without making 2.7.x and 3.0.x and 3.1.x releases as the
>> prerequisites.
>> At some point we did have 4 branches (including a trunk). Ultimately,
>> IMHO, a Java 8 trunk can indeed help with getting more new features into
>> CXF. Java 7 reaches the end of life in two months. I agree things are
>> changing at a much slower rate in the productions. But starting planning
>> for a Java 8 trunk is better be done earlier than later :-)
>>
>> Sergey
>>
>>
>> On 13/02/15 22:32, Jason Pell wrote:
>>
>>> By customers I don't mean my companies customers, I mean users of cxf 2.7
>>>
>>> On Sat, Feb 14, 2015 at 9:30 AM, Jason Pell <ja...@pellcorp.com> wrote:
>>>
>>> From a purely selfish point of view, I hope that 2.7 end of life is
>>>> announced well in advance, as a lot of customers will have to migrate to
>>>> 3.x.
>>>>
>>>> On Sat, Feb 14, 2015 at 4:20 AM, Sergey Beryozkin <sb...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi All,
>>>>>
>>>>> We've had a brief chat with Dan earlier about the possibility of
>>>>> introducing a Java 8 trunk after it was announced JAX-RS 2.1 API would
>>>>> be
>>>>> Java 8 based.
>>>>>
>>>>> I'd like to justify here why IMHO this would be a very good thing for
>>>>> CXF:
>>>>>
>>>>> - Java 8 is recognized to have a lot of new language features that can
>>>>> help with significantly enhancing the capabilities of a given project.
>>>>> Functional programming, security related enhancements, etc, etc. IMHO
>>>>> opening a Java 8 trunk would help us 're-invigorate' the CXF source (all
>>>>> frontends) with respect to the asynchronous, security-related and other
>>>>> processing and will likely lead to the introduction of the new features
>>>>> we
>>>>> can not even think of now. It will also excite the CXF community at
>>>>> large.
>>>>>
>>>>> - JAX-RS 2.1 requires Java8. JAX-RS 2.1 started its work in December
>>>>> 2014
>>>>> and I do expect Jersey and RestEasy teams publishing the snapshots more
>>>>> or
>>>>> less in sync with the ongoing API updates. Many users do want to play
>>>>> with
>>>>> the latest and greatest API asap. Besides, implementing iteratively
>>>>> would
>>>>> make it easier for us to deal with the other commitments we may have.
>>>>>
>>>>> We have 3.1.0 and 3.0.x but there are no major differences between them
>>>>> from a feature point of view except that 3.1.0 is Java 7 based (with
>>>>> some
>>>>> related improvements).
>>>>>
>>>>> So I believe it would be good to have a Java 8 trunk. The major question
>>>>> is when. But I hope it can be opened by the end of this year or possibly
>>>>> even a bit earlier.
>>>>>
>>>>> IMHO the following may make sense:
>>>>>
>>>>> Open it in the end of life for 2.7.x and either 3.1.0 or 3.1.1 releases.
>>>>>
>>>>> 2.7.x is nearly 2.7.15 now and I guess there will be 3 or so 2.7.x
>>>>> releases afterwards max.
>>>>>
>>>>> If 2.7.x can be 'closed' and '3.1.0' released at the same time then IMHO
>>>>> it can just make sense to branch 3.1.x at that point and open a Java 8
>>>>> CXF
>>>>> 4.0 trunk. Otherwise do it after 2.7.x is closed and 3.1.1 is released.
>>>>>
>>>>> Thoughts are welcome
>>>>> Thanks, Sergey
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
Re: Planning for Java8 trunk
Posted by Jason Pell <ja...@pellcorp.com>.
Java 8 support I think is paramount for moving project forward. I just
don't want the death of 2.7 to be a prerequisite :-)
Its probably going to be at least 6 months before I can migrate my own
project to 3.x
On 16/02/2015 6:03 AM, "Sergey Beryozkin" <sb...@gmail.com> wrote:
> Sure. I guess it would be wise to discuss the introduction of
> a Java 8 trunk without making 2.7.x and 3.0.x and 3.1.x releases as the
> prerequisites.
> At some point we did have 4 branches (including a trunk). Ultimately,
> IMHO, a Java 8 trunk can indeed help with getting more new features into
> CXF. Java 7 reaches the end of life in two months. I agree things are
> changing at a much slower rate in the productions. But starting planning
> for a Java 8 trunk is better be done earlier than later :-)
>
> Sergey
>
>
> On 13/02/15 22:32, Jason Pell wrote:
>
>> By customers I don't mean my companies customers, I mean users of cxf 2.7
>>
>> On Sat, Feb 14, 2015 at 9:30 AM, Jason Pell <ja...@pellcorp.com> wrote:
>>
>> From a purely selfish point of view, I hope that 2.7 end of life is
>>> announced well in advance, as a lot of customers will have to migrate to
>>> 3.x.
>>>
>>> On Sat, Feb 14, 2015 at 4:20 AM, Sergey Beryozkin <sb...@gmail.com>
>>> wrote:
>>>
>>> Hi All,
>>>>
>>>> We've had a brief chat with Dan earlier about the possibility of
>>>> introducing a Java 8 trunk after it was announced JAX-RS 2.1 API would
>>>> be
>>>> Java 8 based.
>>>>
>>>> I'd like to justify here why IMHO this would be a very good thing for
>>>> CXF:
>>>>
>>>> - Java 8 is recognized to have a lot of new language features that can
>>>> help with significantly enhancing the capabilities of a given project.
>>>> Functional programming, security related enhancements, etc, etc. IMHO
>>>> opening a Java 8 trunk would help us 're-invigorate' the CXF source (all
>>>> frontends) with respect to the asynchronous, security-related and other
>>>> processing and will likely lead to the introduction of the new features
>>>> we
>>>> can not even think of now. It will also excite the CXF community at
>>>> large.
>>>>
>>>> - JAX-RS 2.1 requires Java8. JAX-RS 2.1 started its work in December
>>>> 2014
>>>> and I do expect Jersey and RestEasy teams publishing the snapshots more
>>>> or
>>>> less in sync with the ongoing API updates. Many users do want to play
>>>> with
>>>> the latest and greatest API asap. Besides, implementing iteratively
>>>> would
>>>> make it easier for us to deal with the other commitments we may have.
>>>>
>>>> We have 3.1.0 and 3.0.x but there are no major differences between them
>>>> from a feature point of view except that 3.1.0 is Java 7 based (with
>>>> some
>>>> related improvements).
>>>>
>>>> So I believe it would be good to have a Java 8 trunk. The major question
>>>> is when. But I hope it can be opened by the end of this year or possibly
>>>> even a bit earlier.
>>>>
>>>> IMHO the following may make sense:
>>>>
>>>> Open it in the end of life for 2.7.x and either 3.1.0 or 3.1.1 releases.
>>>>
>>>> 2.7.x is nearly 2.7.15 now and I guess there will be 3 or so 2.7.x
>>>> releases afterwards max.
>>>>
>>>> If 2.7.x can be 'closed' and '3.1.0' released at the same time then IMHO
>>>> it can just make sense to branch 3.1.x at that point and open a Java 8
>>>> CXF
>>>> 4.0 trunk. Otherwise do it after 2.7.x is closed and 3.1.1 is released.
>>>>
>>>> Thoughts are welcome
>>>> Thanks, Sergey
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>
Re: Planning for Java8 trunk
Posted by Sergey Beryozkin <sb...@gmail.com>.
Sure. I guess it would be wise to discuss the introduction of
a Java 8 trunk without making 2.7.x and 3.0.x and 3.1.x releases as the
prerequisites.
At some point we did have 4 branches (including a trunk). Ultimately,
IMHO, a Java 8 trunk can indeed help with getting more new features into
CXF. Java 7 reaches the end of life in two months. I agree things are
changing at a much slower rate in the productions. But starting planning
for a Java 8 trunk is better be done earlier than later :-)
Sergey
On 13/02/15 22:32, Jason Pell wrote:
> By customers I don't mean my companies customers, I mean users of cxf 2.7
>
> On Sat, Feb 14, 2015 at 9:30 AM, Jason Pell <ja...@pellcorp.com> wrote:
>
>> From a purely selfish point of view, I hope that 2.7 end of life is
>> announced well in advance, as a lot of customers will have to migrate to
>> 3.x.
>>
>> On Sat, Feb 14, 2015 at 4:20 AM, Sergey Beryozkin <sb...@gmail.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> We've had a brief chat with Dan earlier about the possibility of
>>> introducing a Java 8 trunk after it was announced JAX-RS 2.1 API would be
>>> Java 8 based.
>>>
>>> I'd like to justify here why IMHO this would be a very good thing for CXF:
>>>
>>> - Java 8 is recognized to have a lot of new language features that can
>>> help with significantly enhancing the capabilities of a given project.
>>> Functional programming, security related enhancements, etc, etc. IMHO
>>> opening a Java 8 trunk would help us 're-invigorate' the CXF source (all
>>> frontends) with respect to the asynchronous, security-related and other
>>> processing and will likely lead to the introduction of the new features we
>>> can not even think of now. It will also excite the CXF community at large.
>>>
>>> - JAX-RS 2.1 requires Java8. JAX-RS 2.1 started its work in December 2014
>>> and I do expect Jersey and RestEasy teams publishing the snapshots more or
>>> less in sync with the ongoing API updates. Many users do want to play with
>>> the latest and greatest API asap. Besides, implementing iteratively would
>>> make it easier for us to deal with the other commitments we may have.
>>>
>>> We have 3.1.0 and 3.0.x but there are no major differences between them
>>> from a feature point of view except that 3.1.0 is Java 7 based (with some
>>> related improvements).
>>>
>>> So I believe it would be good to have a Java 8 trunk. The major question
>>> is when. But I hope it can be opened by the end of this year or possibly
>>> even a bit earlier.
>>>
>>> IMHO the following may make sense:
>>>
>>> Open it in the end of life for 2.7.x and either 3.1.0 or 3.1.1 releases.
>>>
>>> 2.7.x is nearly 2.7.15 now and I guess there will be 3 or so 2.7.x
>>> releases afterwards max.
>>>
>>> If 2.7.x can be 'closed' and '3.1.0' released at the same time then IMHO
>>> it can just make sense to branch 3.1.x at that point and open a Java 8 CXF
>>> 4.0 trunk. Otherwise do it after 2.7.x is closed and 3.1.1 is released.
>>>
>>> Thoughts are welcome
>>> Thanks, Sergey
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>
Re: Planning for Java8 trunk
Posted by Jason Pell <ja...@pellcorp.com>.
By customers I don't mean my companies customers, I mean users of cxf 2.7
On Sat, Feb 14, 2015 at 9:30 AM, Jason Pell <ja...@pellcorp.com> wrote:
> From a purely selfish point of view, I hope that 2.7 end of life is
> announced well in advance, as a lot of customers will have to migrate to
> 3.x.
>
> On Sat, Feb 14, 2015 at 4:20 AM, Sergey Beryozkin <sb...@gmail.com>
> wrote:
>
>> Hi All,
>>
>> We've had a brief chat with Dan earlier about the possibility of
>> introducing a Java 8 trunk after it was announced JAX-RS 2.1 API would be
>> Java 8 based.
>>
>> I'd like to justify here why IMHO this would be a very good thing for CXF:
>>
>> - Java 8 is recognized to have a lot of new language features that can
>> help with significantly enhancing the capabilities of a given project.
>> Functional programming, security related enhancements, etc, etc. IMHO
>> opening a Java 8 trunk would help us 're-invigorate' the CXF source (all
>> frontends) with respect to the asynchronous, security-related and other
>> processing and will likely lead to the introduction of the new features we
>> can not even think of now. It will also excite the CXF community at large.
>>
>> - JAX-RS 2.1 requires Java8. JAX-RS 2.1 started its work in December 2014
>> and I do expect Jersey and RestEasy teams publishing the snapshots more or
>> less in sync with the ongoing API updates. Many users do want to play with
>> the latest and greatest API asap. Besides, implementing iteratively would
>> make it easier for us to deal with the other commitments we may have.
>>
>> We have 3.1.0 and 3.0.x but there are no major differences between them
>> from a feature point of view except that 3.1.0 is Java 7 based (with some
>> related improvements).
>>
>> So I believe it would be good to have a Java 8 trunk. The major question
>> is when. But I hope it can be opened by the end of this year or possibly
>> even a bit earlier.
>>
>> IMHO the following may make sense:
>>
>> Open it in the end of life for 2.7.x and either 3.1.0 or 3.1.1 releases.
>>
>> 2.7.x is nearly 2.7.15 now and I guess there will be 3 or so 2.7.x
>> releases afterwards max.
>>
>> If 2.7.x can be 'closed' and '3.1.0' released at the same time then IMHO
>> it can just make sense to branch 3.1.x at that point and open a Java 8 CXF
>> 4.0 trunk. Otherwise do it after 2.7.x is closed and 3.1.1 is released.
>>
>> Thoughts are welcome
>> Thanks, Sergey
>>
>>
>>
>>
>>
>>
>>
>
Re: Planning for Java8 trunk
Posted by Jason Pell <ja...@pellcorp.com>.
>From a purely selfish point of view, I hope that 2.7 end of life is
announced well in advance, as a lot of customers will have to migrate to
3.x.
On Sat, Feb 14, 2015 at 4:20 AM, Sergey Beryozkin <sb...@gmail.com>
wrote:
> Hi All,
>
> We've had a brief chat with Dan earlier about the possibility of
> introducing a Java 8 trunk after it was announced JAX-RS 2.1 API would be
> Java 8 based.
>
> I'd like to justify here why IMHO this would be a very good thing for CXF:
>
> - Java 8 is recognized to have a lot of new language features that can
> help with significantly enhancing the capabilities of a given project.
> Functional programming, security related enhancements, etc, etc. IMHO
> opening a Java 8 trunk would help us 're-invigorate' the CXF source (all
> frontends) with respect to the asynchronous, security-related and other
> processing and will likely lead to the introduction of the new features we
> can not even think of now. It will also excite the CXF community at large.
>
> - JAX-RS 2.1 requires Java8. JAX-RS 2.1 started its work in December 2014
> and I do expect Jersey and RestEasy teams publishing the snapshots more or
> less in sync with the ongoing API updates. Many users do want to play with
> the latest and greatest API asap. Besides, implementing iteratively would
> make it easier for us to deal with the other commitments we may have.
>
> We have 3.1.0 and 3.0.x but there are no major differences between them
> from a feature point of view except that 3.1.0 is Java 7 based (with some
> related improvements).
>
> So I believe it would be good to have a Java 8 trunk. The major question
> is when. But I hope it can be opened by the end of this year or possibly
> even a bit earlier.
>
> IMHO the following may make sense:
>
> Open it in the end of life for 2.7.x and either 3.1.0 or 3.1.1 releases.
>
> 2.7.x is nearly 2.7.15 now and I guess there will be 3 or so 2.7.x
> releases afterwards max.
>
> If 2.7.x can be 'closed' and '3.1.0' released at the same time then IMHO
> it can just make sense to branch 3.1.x at that point and open a Java 8 CXF
> 4.0 trunk. Otherwise do it after 2.7.x is closed and 3.1.1 is released.
>
> Thoughts are welcome
> Thanks, Sergey
>
>
>
>
>
>
>