You are viewing a plain text version of this content. The canonical link for it is here.
Posted to httpclient-users@hc.apache.org by Oleg Kalnichevski <ol...@apache.org> on 2013/09/16 14:02:49 UTC
[POLL] Minimal JRE level as of HttpClient 4.4
Folks,
Java 1.5 compatibility has become increasing difficult to maintain and
increasing pointless on top of that. We, as a project, have been
thinking about upgrading minimal JRE level requirement for the
HttpClient 4.4 branch to something newer. While Java 1.6 might be a
reasonable and a conservative choice in terms of stability and adoption,
it actually brings little in terms of new features we could make use of
in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
as well consider upgrading to Java 1.7 which would give us NIO2, full
support for 'try with resources', and probably some other features.
Please let us know what you think and respond to this poll.
All users of HttpClient are encouraged to participate. Every vote will
count.
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[ ] upgrade to Java 1.7: new features are more important.
-------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Andreas Ernst <ae...@ae-online.de>.
Am 16.09.13 14:02, schrieb Oleg Kalnichevski:
> -------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [ ] upgrade to Java 1.6: one step at a time.
> [ ] upgrade to Java 1.7: new features are more important.
> -------------------
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[x] upgrade to Java 1.7: new features are more important.
-------------------
--
ae | Andreas Ernst | IT Spektrum
Postfach 5, 65612 Beselich
Schupbacher Str. 32, 65614 Beselich, Germany
Tel: +49-6484-91002 Fax: +49-6484-91003
ae@ae-online.de | www.ae-online.de
www.tachyon-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
RE: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Pete Keyes <PK...@starbucks.com>.
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[X] upgrade to Java 1.7: new features are more important.
Pete Keyes
(w)206.318.5933; (c)206.914.4134
Starbucks Coffee Co.
2401 Utah Ave S
Seattle, WA. 98134
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Sebastiano Vigna <vi...@di.unimi.it>.
On 16 Sep 2013, at 1:02 PM, Oleg Kalnichevski <ol...@apache.org> wrote:
> -------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [ ] upgrade to Java 1.6: one step at a time.
> [X] upgrade to Java 1.7: new features are more important.
> -------------------
Just consider that there are JVMs, like Azul's, which are still at Java 6.
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Arnaud Quillaud <ar...@quillaud.org>.
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[x] upgrade to Java 1.7: new features are more important.
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Isuru Perera <is...@apache.org>.
On Mon, Sep 16, 2013 at 5:32 PM, Oleg Kalnichevski <ol...@apache.org> wrote:
>
> -------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [ ] upgrade to Java 1.6: one step at a time.
> [X] upgrade to Java 1.7: new features are more important.
> -------------------
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Christopher BROWN <br...@reflexe.fr>.
> -------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [ ] upgrade to Java 1.6: one step at a time.
> [X] upgrade to Java 1.7: new features are more important.
> -------------------
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Dave Roberts <da...@saaconsultants.com>.
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[x] upgrade to Java 1.7: new features are more important.
-------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
RE: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by "David J. Godbey (HQ-LM020)[DIGITAL MANAGEMENT INC.]" <da...@nasa.gov>.
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[X ] upgrade to Java 1.7: new features are more important.
-----Original Message-----
From: Oleg Kalnichevski [mailto:olegk@apache.org]
Sent: Monday, September 16, 2013 8:03 AM
To: httpclient-users@hc.apache.org
Subject: [POLL] Minimal JRE level as of HttpClient 4.4
Folks,
Java 1.5 compatibility has become increasing difficult to maintain and increasing pointless on top of that. We, as a project, have been thinking about upgrading minimal JRE level requirement for the HttpClient 4.4 branch to something newer. While Java 1.6 might be a reasonable and a conservative choice in terms of stability and adoption, it actually brings little in terms of new features we could make use of in HttpClient. Besides, Java 1.6 is officially end of life. So, we might as well consider upgrading to Java 1.7 which would give us NIO2, full support for 'try with resources', and probably some other features.
Please let us know what you think and respond to this poll.
All users of HttpClient are encouraged to participate. Every vote will count.
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[ ] upgrade to Java 1.7: new features are more important.
-------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
RE: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by "KARR, DAVID" <dk...@att.com>.
> -----Original Message-----
> From: Oleg Kalnichevski [mailto:olegk@apache.org]
> Sent: Monday, September 16, 2013 5:03 AM
> To: httpclient-users@hc.apache.org
> Subject: [POLL] Minimal JRE level as of HttpClient 4.4
>
> Folks,
>
> Java 1.5 compatibility has become increasing difficult to maintain and
> increasing pointless on top of that. We, as a project, have been
> thinking about upgrading minimal JRE level requirement for the
> HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> reasonable and a conservative choice in terms of stability and adoption,
> it actually brings little in terms of new features we could make use of
> in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
> as well consider upgrading to Java 1.7 which would give us NIO2, full
> support for 'try with resources', and probably some other features.
>
> Please let us know what you think and respond to this poll.
>
> All users of HttpClient are encouraged to participate. Every vote will
> count.
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[X] upgrade to Java 1.6: one step at a time.
[ ] upgrade to Java 1.7: new features are more important.
-------------------
1.6 may be at EOL, but the version of our principal application framework is only certified at JDK 1.6. We won't be fully upgraded for many months yet.
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Tony Anecito <ad...@yahoo.com>.
Real world still using 1.6. Until it is gone from the public if this compiled to 1.7 byte code it will break in clients using 1.6 jre. I want to switch to 1.7 but too many open source projects still using 1.6 bytecode also.
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[X ] upgrade to Java 1.6: one step at a time.
[] upgrade to Java 1.7: new features are more important.
-------------------
________________________________
From: Johannes Kienzle <jk...@salesforce.com>
To: HttpClient User Discussion <ht...@hc.apache.org>
Sent: Monday, September 16, 2013 12:30 PM
Subject: Re: [POLL] Minimal JRE level as of HttpClient 4.4
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[X] upgrade to Java 1.7: new features are more important.
-------------------
On Mon, Sep 16, 2013 at 1:19 PM, Erik Pilz <er...@pilzner.com> wrote:
> -------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [ ] upgrade to Java 1.6: one step at a time.
> [X] upgrade to Java 1.7: new features are more important.
> -------------------
>
>
> On Mon, Sep 16, 2013 at 5:02 AM, Oleg Kalnichevski <ol...@apache.org>
> wrote:
>
> > Folks,
> >
> > Java 1.5 compatibility has become increasing difficult to maintain and
> > increasing pointless on top of that. We, as a project, have been
> > thinking about upgrading minimal JRE level requirement for the
> > HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> > reasonable and a conservative choice in terms of stability and adoption,
> > it actually brings little in terms of new features we could make use of
> > in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
> > as well consider upgrading to Java 1.7 which would give us NIO2, full
> > support for 'try with resources', and probably some other features.
> >
> > Please let us know what you think and respond to this poll.
> >
> > All users of HttpClient are encouraged to participate. Every vote will
> > count.
> >
> > -------------------
> > [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> > [ ] upgrade to Java 1.6: one step at a time.
> > [ ] upgrade to Java 1.7: new features are more important.
> > -------------------
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: mailto:httpclient-users-unsubscribe@hc.apache.org
> > For additional commands, e-mail: mailto:httpclient-users-help@hc.apache.org
> >
> >
>
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Johannes Kienzle <jk...@salesforce.com>.
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[X] upgrade to Java 1.7: new features are more important.
-------------------
On Mon, Sep 16, 2013 at 1:19 PM, Erik Pilz <er...@pilzner.com> wrote:
> -------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [ ] upgrade to Java 1.6: one step at a time.
> [X] upgrade to Java 1.7: new features are more important.
> -------------------
>
>
> On Mon, Sep 16, 2013 at 5:02 AM, Oleg Kalnichevski <ol...@apache.org>
> wrote:
>
> > Folks,
> >
> > Java 1.5 compatibility has become increasing difficult to maintain and
> > increasing pointless on top of that. We, as a project, have been
> > thinking about upgrading minimal JRE level requirement for the
> > HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> > reasonable and a conservative choice in terms of stability and adoption,
> > it actually brings little in terms of new features we could make use of
> > in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
> > as well consider upgrading to Java 1.7 which would give us NIO2, full
> > support for 'try with resources', and probably some other features.
> >
> > Please let us know what you think and respond to this poll.
> >
> > All users of HttpClient are encouraged to participate. Every vote will
> > count.
> >
> > -------------------
> > [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> > [ ] upgrade to Java 1.6: one step at a time.
> > [ ] upgrade to Java 1.7: new features are more important.
> > -------------------
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> > For additional commands, e-mail: httpclient-users-help@hc.apache.org
> >
> >
>
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Erik Pilz <er...@pilzner.com>.
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[X] upgrade to Java 1.7: new features are more important.
-------------------
On Mon, Sep 16, 2013 at 5:02 AM, Oleg Kalnichevski <ol...@apache.org> wrote:
> Folks,
>
> Java 1.5 compatibility has become increasing difficult to maintain and
> increasing pointless on top of that. We, as a project, have been
> thinking about upgrading minimal JRE level requirement for the
> HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> reasonable and a conservative choice in terms of stability and adoption,
> it actually brings little in terms of new features we could make use of
> in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
> as well consider upgrading to Java 1.7 which would give us NIO2, full
> support for 'try with resources', and probably some other features.
>
> Please let us know what you think and respond to this poll.
>
> All users of HttpClient are encouraged to participate. Every vote will
> count.
>
> -------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [ ] upgrade to Java 1.6: one step at a time.
> [ ] upgrade to Java 1.7: new features are more important.
> -------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>
>
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Ronald Brill <rb...@rbri.de>.
>-------------------
>[ ] keep Java 1.5 compatibility: no good reason to upgrade.
>[x] upgrade to Java 1.6: one step at a time.
>[ ] upgrade to Java 1.7: new features are more important.
>-------------------
RBRi
--------------------------
Wetator
Smart web application testing
http://www.wetator.org
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Alexey Panchenko <al...@gmail.com>.
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[x] upgrade to Java 1.6: one step at a time.
[ ] upgrade to Java 1.7: new features are more important.
For big projects it takes longer to upgrade JVM.
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Geoff Capper <gc...@bigpond.com>.
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[X] upgrade to Java 1.7: new features are more important.
-------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
HttpClient 4.4 time line; Re: [POLL] Minimal JRE level as of
HttpClient 4.4
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Mon, 2013-09-16 at 12:36 -0700, Noah Levitt wrote:
> The timeline for 4.4 might have some bearing on this. Do we have an
> idea approximately when to expect 4.4 final?
>
> Noah
>
No time line yet. However given a fairly small set of features planned
for 4.4 (Integrated Windows Auth and the latest cookie spec) 4.4
development is likely to take about 3 to 6 months.
Oleg
> On Mon, Sep 16, 2013 at 5:02 AM, Oleg Kalnichevski <ol...@apache.org> wrote:
> > Folks,
> >
> > Java 1.5 compatibility has become increasing difficult to maintain and
> > increasing pointless on top of that. We, as a project, have been
> > thinking about upgrading minimal JRE level requirement for the
> > HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> > reasonable and a conservative choice in terms of stability and adoption,
> > it actually brings little in terms of new features we could make use of
> > in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
> > as well consider upgrading to Java 1.7 which would give us NIO2, full
> > support for 'try with resources', and probably some other features.
> >
> > Please let us know what you think and respond to this poll.
> >
> > All users of HttpClient are encouraged to participate. Every vote will
> > count.
> >
> > -------------------
> > [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> > [ ] upgrade to Java 1.6: one step at a time.
> > [ ] upgrade to Java 1.7: new features are more important.
> > -------------------
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> > For additional commands, e-mail: httpclient-users-help@hc.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Noah Levitt <nl...@archive.org>.
The timeline for 4.4 might have some bearing on this. Do we have an
idea approximately when to expect 4.4 final?
Noah
On Mon, Sep 16, 2013 at 5:02 AM, Oleg Kalnichevski <ol...@apache.org> wrote:
> Folks,
>
> Java 1.5 compatibility has become increasing difficult to maintain and
> increasing pointless on top of that. We, as a project, have been
> thinking about upgrading minimal JRE level requirement for the
> HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> reasonable and a conservative choice in terms of stability and adoption,
> it actually brings little in terms of new features we could make use of
> in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
> as well consider upgrading to Java 1.7 which would give us NIO2, full
> support for 'try with resources', and probably some other features.
>
> Please let us know what you think and respond to this poll.
>
> All users of HttpClient are encouraged to participate. Every vote will
> count.
>
> -------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [ ] upgrade to Java 1.6: one step at a time.
> [ ] upgrade to Java 1.7: new features are more important.
> -------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
RE: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Joan Balagueró <jo...@grupoventus.com>.
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[X] upgrade to Java 1.6: one step at a time.
[ ] upgrade to Java 1.7: new features are more important.
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Ken Krugler <kk...@transpac.com>.
On Sep 16, 2013, at 5:02am, Oleg Kalnichevski wrote:
> Folks,
>
> Java 1.5 compatibility has become increasing difficult to maintain and
> increasing pointless on top of that. We, as a project, have been
> thinking about upgrading minimal JRE level requirement for the
> HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> reasonable and a conservative choice in terms of stability and adoption,
> it actually brings little in terms of new features we could make use of
> in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
> as well consider upgrading to Java 1.7 which would give us NIO2, full
> support for 'try with resources', and probably some other features.
>
> Please let us know what you think and respond to this poll.
>
> All users of HttpClient are encouraged to participate. Every vote will
> count.
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[X] upgrade to Java 1.6: one step at a time.
[ ] upgrade to Java 1.7: new features are more important.
--------------------------
Ken Krugler
+1 530-210-6378
http://www.scaleunlimited.com
custom big data solutions & training
Hadoop, Cascading, Cassandra & Solr
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by R Smith <ry...@gmail.com>.
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[X] upgrade to Java 1.7: new features are more important.
On Mon, Sep 16, 2013 at 8:02 AM, Oleg Kalnichevski <ol...@apache.org> wrote:
> Folks,
>
> Java 1.5 compatibility has become increasing difficult to maintain and
> increasing pointless on top of that. We, as a project, have been
> thinking about upgrading minimal JRE level requirement for the
> HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> reasonable and a conservative choice in terms of stability and adoption,
> it actually brings little in terms of new features we could make use of
> in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
> as well consider upgrading to Java 1.7 which would give us NIO2, full
> support for 'try with resources', and probably some other features.
>
> Please let us know what you think and respond to this poll.
>
> All users of HttpClient are encouraged to participate. Every vote will
> count.
>
> -------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [ ] upgrade to Java 1.6: one step at a time.
> [ ] upgrade to Java 1.7: new features are more important.
> -------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>
>
Re: Android / Dalvik compatibility; was Re: [POLL] Minimal JRE
level as of HttpClient 4.4
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Sun, 2013-09-22 at 00:56 +0700, Alexey Panchenko wrote:
> try-with-resources is just a syntax sugar -
> http://docs.oracle.com/javase/specs/jls/se7/html/jls-14.html#jls-14.20.3
> It simplifies the code, but it is not an improvement for users.
>
> Alex
>
Well, kind of. It also comes with support for #addSuppressed.
Oleg
>
> On Sat, Sep 21, 2013 at 10:04 PM, Oleg Kalnichevski <ol...@apache.org>wrote:
>
> > On Sat, 2013-09-21 at 16:52 +0200, Christopher BROWN wrote:
> > > I agree in principle, as a 7+ 4.4 release does not imply withdrawal or
> > > self-destruction of previous versions.
> > >
> > > I am curious to know exactly what Java 7 features would be used in HTTP
> > > client.
> > >
> >
> > It would be mainly try-with-resources [1] and _potentially_ NIO2 [2] for
> > file based caching in HttpAsyncClient.
> >
> > Oleg
> >
> > [1]
> >
> > http://docs.oracle.com/javase/7/docs/technotes/guides/language/try-with-resources.html
> > [2] http://docs.oracle.com/javase/tutorial/essential/io/file.html
> >
> > > --
> > > Christopher
> > > Le 21 sept. 2013 16:24, "Gary Gregory" <ga...@gmail.com> a écrit
> > :
> > >
> > > > On Sat, Sep 21, 2013 at 9:59 AM, Oleg Kalnichevski <ol...@apache.org>
> > > > wrote:
> > > >
> > > > > On Sat, 2013-09-21 at 09:04 -0400, Gary Gregory wrote:
> > > > > > On Sep 21, 2013, at 7:23, Oleg Kalnichevski <ol...@apache.org>
> > wrote:
> > > > > >
> > > > > > > On Fri, 2013-09-20 at 21:28 +0100, sebb wrote:
> > > > > > >> On 16 September 2013 13:02, Oleg Kalnichevski <olegk@apache.org
> > >
> > > > > wrote:
> > > > > > >>> Folks,
> > > > > > >>>
> > > > > > >>> Java 1.5 compatibility has become increasing difficult to
> > maintain
> > > > > and
> > > > > > >>> increasing pointless on top of that. We, as a project, have
> > been
> > > > > > >>> thinking about upgrading minimal JRE level requirement for the
> > > > > > >>> HttpClient 4.4 branch to something newer. While Java 1.6 might
> > be a
> > > > > > >>> reasonable and a conservative choice in terms of stability and
> > > > > adoption,
> > > > > > >>> it actually brings little in terms of new features we could
> > make
> > > > use
> > > > > of
> > > > > > >>> in HttpClient. Besides, Java 1.6 is officially end of life.
> > So, we
> > > > > might
> > > > > > >>> as well consider upgrading to Java 1.7 which would give us
> > NIO2,
> > > > full
> > > > > > >>> support for 'try with resources', and probably some other
> > features.
> > > > > > >>>
> > > > > > >>> Please let us know what you think and respond to this poll.
> > > > > > >>>
> > > > > > >>> All users of HttpClient are encouraged to participate. Every
> > vote
> > > > > will
> > > > > > >>> count.
> > > > > > >>>
> > > > > > >
> > > > > > > This is actually a pretty good point. I completely forgot
> > Android was
> > > > > > > still at 1.6 level.
> > > > > >
> > > > > > So what? We are at Google's mercy? Who knows when A will support
> > Java
> > > > > > 7 or 8 if ever.
> > > > > >
> > > > > > Gary
> > > > > > >
> > > > >
> > > > > This is not about pleasing Google. I would not take a squat next to
> > > > > those people given how badly they crewed us over with HttpClient 4.0.
> > > > > However, we still ought to take interests of Android developers into
> > > > > consideration. If we do not immediately start making use of Java 1.7
> > > > > features, we gain nothing by making lives of Android developers even
> > > > > more difficult.
> > > > >
> > > >
> > > > Here is how I see it:
> > > >
> > > > Our software does not self-update itself and break a Android apps. If a
> > > > developers, wants features or bug fixes in a new version, he or she
> > > > evaluates that version and decides if it is appropriate for their use
> > case.
> > > >
> > > > If the HttpComponents community decides that the best path for the
> > project
> > > > is Java 6, then later 7, that's great, it's a measured step to J6,
> > with J7
> > > > coming next. But sooner or later, Java 7 and 8 are going to come into
> > play.
> > > > If the HttpComponents community decides that Java 7 is the way to go
> > > > forward now, then that's great too.
> > > >
> > > > If some developers want to stay on Android/Java 6 and they do not want
> > to
> > > > contribute time and effort into a Java 6 based HttpComponents (in that
> > > > branch), then they should consider joining us, otherwise, it's
> > dragging us
> > > > down.
> > > >
> > > > The overwhelming response to this thread has been to go to Java 7
> > straight
> > > > away. Granted it's just a [POLL] and not a [VOTE], it still reflect the
> > > > interest of the community.
> > > >
> > > > Gary
> > > >
> > > >
> > > > > Oleg
> > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> > > > > For additional commands, e-mail: httpclient-users-help@hc.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > > > Java Persistence with Hibernate, Second Edition<
> > > > http://www.manning.com/bauer3/>
> > > > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> > > > Spring Batch in Action <http://www.manning.com/templier/>
> > > > Blog: http://garygregory.wordpress.com
> > > > Home: http://garygregory.com/
> > > > Tweet! http://twitter.com/GaryGregory
> > > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> > For additional commands, e-mail: httpclient-users-help@hc.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: Android / Dalvik compatibility; was Re: [POLL] Minimal JRE level
as of HttpClient 4.4
Posted by Alexey Panchenko <al...@gmail.com>.
try-with-resources is just a syntax sugar -
http://docs.oracle.com/javase/specs/jls/se7/html/jls-14.html#jls-14.20.3
It simplifies the code, but it is not an improvement for users.
Alex
On Sat, Sep 21, 2013 at 10:04 PM, Oleg Kalnichevski <ol...@apache.org>wrote:
> On Sat, 2013-09-21 at 16:52 +0200, Christopher BROWN wrote:
> > I agree in principle, as a 7+ 4.4 release does not imply withdrawal or
> > self-destruction of previous versions.
> >
> > I am curious to know exactly what Java 7 features would be used in HTTP
> > client.
> >
>
> It would be mainly try-with-resources [1] and _potentially_ NIO2 [2] for
> file based caching in HttpAsyncClient.
>
> Oleg
>
> [1]
>
> http://docs.oracle.com/javase/7/docs/technotes/guides/language/try-with-resources.html
> [2] http://docs.oracle.com/javase/tutorial/essential/io/file.html
>
> > --
> > Christopher
> > Le 21 sept. 2013 16:24, "Gary Gregory" <ga...@gmail.com> a écrit
> :
> >
> > > On Sat, Sep 21, 2013 at 9:59 AM, Oleg Kalnichevski <ol...@apache.org>
> > > wrote:
> > >
> > > > On Sat, 2013-09-21 at 09:04 -0400, Gary Gregory wrote:
> > > > > On Sep 21, 2013, at 7:23, Oleg Kalnichevski <ol...@apache.org>
> wrote:
> > > > >
> > > > > > On Fri, 2013-09-20 at 21:28 +0100, sebb wrote:
> > > > > >> On 16 September 2013 13:02, Oleg Kalnichevski <olegk@apache.org
> >
> > > > wrote:
> > > > > >>> Folks,
> > > > > >>>
> > > > > >>> Java 1.5 compatibility has become increasing difficult to
> maintain
> > > > and
> > > > > >>> increasing pointless on top of that. We, as a project, have
> been
> > > > > >>> thinking about upgrading minimal JRE level requirement for the
> > > > > >>> HttpClient 4.4 branch to something newer. While Java 1.6 might
> be a
> > > > > >>> reasonable and a conservative choice in terms of stability and
> > > > adoption,
> > > > > >>> it actually brings little in terms of new features we could
> make
> > > use
> > > > of
> > > > > >>> in HttpClient. Besides, Java 1.6 is officially end of life.
> So, we
> > > > might
> > > > > >>> as well consider upgrading to Java 1.7 which would give us
> NIO2,
> > > full
> > > > > >>> support for 'try with resources', and probably some other
> features.
> > > > > >>>
> > > > > >>> Please let us know what you think and respond to this poll.
> > > > > >>>
> > > > > >>> All users of HttpClient are encouraged to participate. Every
> vote
> > > > will
> > > > > >>> count.
> > > > > >>>
> > > > > >
> > > > > > This is actually a pretty good point. I completely forgot
> Android was
> > > > > > still at 1.6 level.
> > > > >
> > > > > So what? We are at Google's mercy? Who knows when A will support
> Java
> > > > > 7 or 8 if ever.
> > > > >
> > > > > Gary
> > > > > >
> > > >
> > > > This is not about pleasing Google. I would not take a squat next to
> > > > those people given how badly they crewed us over with HttpClient 4.0.
> > > > However, we still ought to take interests of Android developers into
> > > > consideration. If we do not immediately start making use of Java 1.7
> > > > features, we gain nothing by making lives of Android developers even
> > > > more difficult.
> > > >
> > >
> > > Here is how I see it:
> > >
> > > Our software does not self-update itself and break a Android apps. If a
> > > developers, wants features or bug fixes in a new version, he or she
> > > evaluates that version and decides if it is appropriate for their use
> case.
> > >
> > > If the HttpComponents community decides that the best path for the
> project
> > > is Java 6, then later 7, that's great, it's a measured step to J6,
> with J7
> > > coming next. But sooner or later, Java 7 and 8 are going to come into
> play.
> > > If the HttpComponents community decides that Java 7 is the way to go
> > > forward now, then that's great too.
> > >
> > > If some developers want to stay on Android/Java 6 and they do not want
> to
> > > contribute time and effort into a Java 6 based HttpComponents (in that
> > > branch), then they should consider joining us, otherwise, it's
> dragging us
> > > down.
> > >
> > > The overwhelming response to this thread has been to go to Java 7
> straight
> > > away. Granted it's just a [POLL] and not a [VOTE], it still reflect the
> > > interest of the community.
> > >
> > > Gary
> > >
> > >
> > > > Oleg
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> > > > For additional commands, e-mail: httpclient-users-help@hc.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > > Java Persistence with Hibernate, Second Edition<
> > > http://www.manning.com/bauer3/>
> > > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> > > Spring Batch in Action <http://www.manning.com/templier/>
> > > Blog: http://garygregory.wordpress.com
> > > Home: http://garygregory.com/
> > > Tweet! http://twitter.com/GaryGregory
> > >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>
>
Re: Android / Dalvik compatibility; was Re: [POLL] Minimal JRE
level as of HttpClient 4.4
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Sat, 2013-09-21 at 16:52 +0200, Christopher BROWN wrote:
> I agree in principle, as a 7+ 4.4 release does not imply withdrawal or
> self-destruction of previous versions.
>
> I am curious to know exactly what Java 7 features would be used in HTTP
> client.
>
It would be mainly try-with-resources [1] and _potentially_ NIO2 [2] for
file based caching in HttpAsyncClient.
Oleg
[1]
http://docs.oracle.com/javase/7/docs/technotes/guides/language/try-with-resources.html
[2] http://docs.oracle.com/javase/tutorial/essential/io/file.html
> --
> Christopher
> Le 21 sept. 2013 16:24, "Gary Gregory" <ga...@gmail.com> a écrit :
>
> > On Sat, Sep 21, 2013 at 9:59 AM, Oleg Kalnichevski <ol...@apache.org>
> > wrote:
> >
> > > On Sat, 2013-09-21 at 09:04 -0400, Gary Gregory wrote:
> > > > On Sep 21, 2013, at 7:23, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > >
> > > > > On Fri, 2013-09-20 at 21:28 +0100, sebb wrote:
> > > > >> On 16 September 2013 13:02, Oleg Kalnichevski <ol...@apache.org>
> > > wrote:
> > > > >>> Folks,
> > > > >>>
> > > > >>> Java 1.5 compatibility has become increasing difficult to maintain
> > > and
> > > > >>> increasing pointless on top of that. We, as a project, have been
> > > > >>> thinking about upgrading minimal JRE level requirement for the
> > > > >>> HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> > > > >>> reasonable and a conservative choice in terms of stability and
> > > adoption,
> > > > >>> it actually brings little in terms of new features we could make
> > use
> > > of
> > > > >>> in HttpClient. Besides, Java 1.6 is officially end of life. So, we
> > > might
> > > > >>> as well consider upgrading to Java 1.7 which would give us NIO2,
> > full
> > > > >>> support for 'try with resources', and probably some other features.
> > > > >>>
> > > > >>> Please let us know what you think and respond to this poll.
> > > > >>>
> > > > >>> All users of HttpClient are encouraged to participate. Every vote
> > > will
> > > > >>> count.
> > > > >>>
> > > > >
> > > > > This is actually a pretty good point. I completely forgot Android was
> > > > > still at 1.6 level.
> > > >
> > > > So what? We are at Google's mercy? Who knows when A will support Java
> > > > 7 or 8 if ever.
> > > >
> > > > Gary
> > > > >
> > >
> > > This is not about pleasing Google. I would not take a squat next to
> > > those people given how badly they crewed us over with HttpClient 4.0.
> > > However, we still ought to take interests of Android developers into
> > > consideration. If we do not immediately start making use of Java 1.7
> > > features, we gain nothing by making lives of Android developers even
> > > more difficult.
> > >
> >
> > Here is how I see it:
> >
> > Our software does not self-update itself and break a Android apps. If a
> > developers, wants features or bug fixes in a new version, he or she
> > evaluates that version and decides if it is appropriate for their use case.
> >
> > If the HttpComponents community decides that the best path for the project
> > is Java 6, then later 7, that's great, it's a measured step to J6, with J7
> > coming next. But sooner or later, Java 7 and 8 are going to come into play.
> > If the HttpComponents community decides that Java 7 is the way to go
> > forward now, then that's great too.
> >
> > If some developers want to stay on Android/Java 6 and they do not want to
> > contribute time and effort into a Java 6 based HttpComponents (in that
> > branch), then they should consider joining us, otherwise, it's dragging us
> > down.
> >
> > The overwhelming response to this thread has been to go to Java 7 straight
> > away. Granted it's just a [POLL] and not a [VOTE], it still reflect the
> > interest of the community.
> >
> > Gary
> >
> >
> > > Oleg
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> > > For additional commands, e-mail: httpclient-users-help@hc.apache.org
> > >
> > >
> >
> >
> > --
> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > Java Persistence with Hibernate, Second Edition<
> > http://www.manning.com/bauer3/>
> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> > Spring Batch in Action <http://www.manning.com/templier/>
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: Android / Dalvik compatibility; was Re: [POLL] Minimal JRE level
as of HttpClient 4.4
Posted by Christopher BROWN <br...@reflexe.fr>.
I agree in principle, as a 7+ 4.4 release does not imply withdrawal or
self-destruction of previous versions.
I am curious to know exactly what Java 7 features would be used in HTTP
client.
--
Christopher
Le 21 sept. 2013 16:24, "Gary Gregory" <ga...@gmail.com> a écrit :
> On Sat, Sep 21, 2013 at 9:59 AM, Oleg Kalnichevski <ol...@apache.org>
> wrote:
>
> > On Sat, 2013-09-21 at 09:04 -0400, Gary Gregory wrote:
> > > On Sep 21, 2013, at 7:23, Oleg Kalnichevski <ol...@apache.org> wrote:
> > >
> > > > On Fri, 2013-09-20 at 21:28 +0100, sebb wrote:
> > > >> On 16 September 2013 13:02, Oleg Kalnichevski <ol...@apache.org>
> > wrote:
> > > >>> Folks,
> > > >>>
> > > >>> Java 1.5 compatibility has become increasing difficult to maintain
> > and
> > > >>> increasing pointless on top of that. We, as a project, have been
> > > >>> thinking about upgrading minimal JRE level requirement for the
> > > >>> HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> > > >>> reasonable and a conservative choice in terms of stability and
> > adoption,
> > > >>> it actually brings little in terms of new features we could make
> use
> > of
> > > >>> in HttpClient. Besides, Java 1.6 is officially end of life. So, we
> > might
> > > >>> as well consider upgrading to Java 1.7 which would give us NIO2,
> full
> > > >>> support for 'try with resources', and probably some other features.
> > > >>>
> > > >>> Please let us know what you think and respond to this poll.
> > > >>>
> > > >>> All users of HttpClient are encouraged to participate. Every vote
> > will
> > > >>> count.
> > > >>>
> > > >
> > > > This is actually a pretty good point. I completely forgot Android was
> > > > still at 1.6 level.
> > >
> > > So what? We are at Google's mercy? Who knows when A will support Java
> > > 7 or 8 if ever.
> > >
> > > Gary
> > > >
> >
> > This is not about pleasing Google. I would not take a squat next to
> > those people given how badly they crewed us over with HttpClient 4.0.
> > However, we still ought to take interests of Android developers into
> > consideration. If we do not immediately start making use of Java 1.7
> > features, we gain nothing by making lives of Android developers even
> > more difficult.
> >
>
> Here is how I see it:
>
> Our software does not self-update itself and break a Android apps. If a
> developers, wants features or bug fixes in a new version, he or she
> evaluates that version and decides if it is appropriate for their use case.
>
> If the HttpComponents community decides that the best path for the project
> is Java 6, then later 7, that's great, it's a measured step to J6, with J7
> coming next. But sooner or later, Java 7 and 8 are going to come into play.
> If the HttpComponents community decides that Java 7 is the way to go
> forward now, then that's great too.
>
> If some developers want to stay on Android/Java 6 and they do not want to
> contribute time and effort into a Java 6 based HttpComponents (in that
> branch), then they should consider joining us, otherwise, it's dragging us
> down.
>
> The overwhelming response to this thread has been to go to Java 7 straight
> away. Granted it's just a [POLL] and not a [VOTE], it still reflect the
> interest of the community.
>
> Gary
>
>
> > Oleg
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> > For additional commands, e-mail: httpclient-users-help@hc.apache.org
> >
> >
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition<
> http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
Re: Android / Dalvik compatibility; was Re: [POLL] Minimal JRE level
as of HttpClient 4.4
Posted by Gary Gregory <ga...@gmail.com>.
On Sat, Sep 21, 2013 at 9:59 AM, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Sat, 2013-09-21 at 09:04 -0400, Gary Gregory wrote:
> > On Sep 21, 2013, at 7:23, Oleg Kalnichevski <ol...@apache.org> wrote:
> >
> > > On Fri, 2013-09-20 at 21:28 +0100, sebb wrote:
> > >> On 16 September 2013 13:02, Oleg Kalnichevski <ol...@apache.org>
> wrote:
> > >>> Folks,
> > >>>
> > >>> Java 1.5 compatibility has become increasing difficult to maintain
> and
> > >>> increasing pointless on top of that. We, as a project, have been
> > >>> thinking about upgrading minimal JRE level requirement for the
> > >>> HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> > >>> reasonable and a conservative choice in terms of stability and
> adoption,
> > >>> it actually brings little in terms of new features we could make use
> of
> > >>> in HttpClient. Besides, Java 1.6 is officially end of life. So, we
> might
> > >>> as well consider upgrading to Java 1.7 which would give us NIO2, full
> > >>> support for 'try with resources', and probably some other features.
> > >>>
> > >>> Please let us know what you think and respond to this poll.
> > >>>
> > >>> All users of HttpClient are encouraged to participate. Every vote
> will
> > >>> count.
> > >>>
> > >
> > > This is actually a pretty good point. I completely forgot Android was
> > > still at 1.6 level.
> >
> > So what? We are at Google's mercy? Who knows when A will support Java
> > 7 or 8 if ever.
> >
> > Gary
> > >
>
> This is not about pleasing Google. I would not take a squat next to
> those people given how badly they crewed us over with HttpClient 4.0.
> However, we still ought to take interests of Android developers into
> consideration. If we do not immediately start making use of Java 1.7
> features, we gain nothing by making lives of Android developers even
> more difficult.
>
Here is how I see it:
Our software does not self-update itself and break a Android apps. If a
developers, wants features or bug fixes in a new version, he or she
evaluates that version and decides if it is appropriate for their use case.
If the HttpComponents community decides that the best path for the project
is Java 6, then later 7, that's great, it's a measured step to J6, with J7
coming next. But sooner or later, Java 7 and 8 are going to come into play.
If the HttpComponents community decides that Java 7 is the way to go
forward now, then that's great too.
If some developers want to stay on Android/Java 6 and they do not want to
contribute time and effort into a Java 6 based HttpComponents (in that
branch), then they should consider joining us, otherwise, it's dragging us
down.
The overwhelming response to this thread has been to go to Java 7 straight
away. Granted it's just a [POLL] and not a [VOTE], it still reflect the
interest of the community.
Gary
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Android / Dalvik compatibility; was Re: [POLL] Minimal JRE level as
of HttpClient 4.4
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Sat, 2013-09-21 at 09:04 -0400, Gary Gregory wrote:
> On Sep 21, 2013, at 7:23, Oleg Kalnichevski <ol...@apache.org> wrote:
>
> > On Fri, 2013-09-20 at 21:28 +0100, sebb wrote:
> >> On 16 September 2013 13:02, Oleg Kalnichevski <ol...@apache.org> wrote:
> >>> Folks,
> >>>
> >>> Java 1.5 compatibility has become increasing difficult to maintain and
> >>> increasing pointless on top of that. We, as a project, have been
> >>> thinking about upgrading minimal JRE level requirement for the
> >>> HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> >>> reasonable and a conservative choice in terms of stability and adoption,
> >>> it actually brings little in terms of new features we could make use of
> >>> in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
> >>> as well consider upgrading to Java 1.7 which would give us NIO2, full
> >>> support for 'try with resources', and probably some other features.
> >>>
> >>> Please let us know what you think and respond to this poll.
> >>>
> >>> All users of HttpClient are encouraged to participate. Every vote will
> >>> count.
> >>>
> >
> > This is actually a pretty good point. I completely forgot Android was
> > still at 1.6 level.
>
> So what? We are at Google's mercy? Who knows when A will support Java
> 7 or 8 if ever.
>
> Gary
> >
This is not about pleasing Google. I would not take a squat next to
those people given how badly they crewed us over with HttpClient 4.0.
However, we still ought to take interests of Android developers into
consideration. If we do not immediately start making use of Java 1.7
features, we gain nothing by making lives of Android developers even
more difficult.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Gary Gregory <ga...@gmail.com>.
On Sep 21, 2013, at 7:23, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Fri, 2013-09-20 at 21:28 +0100, sebb wrote:
>> On 16 September 2013 13:02, Oleg Kalnichevski <ol...@apache.org> wrote:
>>> Folks,
>>>
>>> Java 1.5 compatibility has become increasing difficult to maintain and
>>> increasing pointless on top of that. We, as a project, have been
>>> thinking about upgrading minimal JRE level requirement for the
>>> HttpClient 4.4 branch to something newer. While Java 1.6 might be a
>>> reasonable and a conservative choice in terms of stability and adoption,
>>> it actually brings little in terms of new features we could make use of
>>> in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
>>> as well consider upgrading to Java 1.7 which would give us NIO2, full
>>> support for 'try with resources', and probably some other features.
>>>
>>> Please let us know what you think and respond to this poll.
>>>
>>> All users of HttpClient are encouraged to participate. Every vote will
>>> count.
>>>
>
> This is actually a pretty good point. I completely forgot Android was
> still at 1.6 level.
So what? We are at Google's mercy? Who knows when A will support Java
7 or 8 if ever.
Gary
>
> [X] upgrade to Java 1.6: one step at a time
>
> Oleg
>
>>> -------------------
>>> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
>>> [X] upgrade to Java 1.6: one step at a time.
>>
>> This potentially allows HC to be used with Android code.
>>
>>> [ ] upgrade to Java 1.7: new features are more important.
>>> -------------------
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
>>> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
>> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Fri, 2013-09-20 at 21:28 +0100, sebb wrote:
> On 16 September 2013 13:02, Oleg Kalnichevski <ol...@apache.org> wrote:
> > Folks,
> >
> > Java 1.5 compatibility has become increasing difficult to maintain and
> > increasing pointless on top of that. We, as a project, have been
> > thinking about upgrading minimal JRE level requirement for the
> > HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> > reasonable and a conservative choice in terms of stability and adoption,
> > it actually brings little in terms of new features we could make use of
> > in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
> > as well consider upgrading to Java 1.7 which would give us NIO2, full
> > support for 'try with resources', and probably some other features.
> >
> > Please let us know what you think and respond to this poll.
> >
> > All users of HttpClient are encouraged to participate. Every vote will
> > count.
> >
This is actually a pretty good point. I completely forgot Android was
still at 1.6 level.
[X] upgrade to Java 1.6: one step at a time
Oleg
> > -------------------
> > [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> > [X] upgrade to Java 1.6: one step at a time.
>
> This potentially allows HC to be used with Android code.
>
> > [ ] upgrade to Java 1.7: new features are more important.
> > -------------------
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> > For additional commands, e-mail: httpclient-users-help@hc.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by sebb <se...@gmail.com>.
On 16 September 2013 13:02, Oleg Kalnichevski <ol...@apache.org> wrote:
> Folks,
>
> Java 1.5 compatibility has become increasing difficult to maintain and
> increasing pointless on top of that. We, as a project, have been
> thinking about upgrading minimal JRE level requirement for the
> HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> reasonable and a conservative choice in terms of stability and adoption,
> it actually brings little in terms of new features we could make use of
> in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
> as well consider upgrading to Java 1.7 which would give us NIO2, full
> support for 'try with resources', and probably some other features.
>
> Please let us know what you think and respond to this poll.
>
> All users of HttpClient are encouraged to participate. Every vote will
> count.
>
> -------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [X] upgrade to Java 1.6: one step at a time.
This potentially allows HC to be used with Android code.
> [ ] upgrade to Java 1.7: new features are more important.
> -------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Jordi Domingo Borràs <jo...@gmail.com>.
-------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [ ] upgrade to Java 1.6: one step at a time.
> [X] upgrade to Java 1.7: new features are more important.
> -------------------
>
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Gary Gregory <ga...@gmail.com>.
On Mon, Sep 16, 2013 at 8:02 AM, Oleg Kalnichevski <ol...@apache.org> wrote:
> Folks,
>
> Java 1.5 compatibility has become increasing difficult to maintain and
> increasing pointless on top of that. We, as a project, have been
> thinking about upgrading minimal JRE level requirement for the
> HttpClient 4.4 branch to something newer. While Java 1.6 might be a
> reasonable and a conservative choice in terms of stability and adoption,
> it actually brings little in terms of new features we could make use of
> in HttpClient. Besides, Java 1.6 is officially end of life. So, we might
> as well consider upgrading to Java 1.7 which would give us NIO2, full
> support for 'try with resources', and probably some other features.
>
> Please let us know what you think and respond to this poll.
>
> All users of HttpClient are encouraged to participate. Every vote will
> count.
>
> -------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [ ] upgrade to Java 1.6: one step at a time.
> [X] upgrade to Java 1.7: new features are more important.
> -------------------
>
> Gary
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by Francois-Xavier Bonnet <fr...@centraliens.net>.
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[X ] upgrade to Java 1.7: new features are more important.
-------------------
2013/9/16 Kimpton, C (Chris) <Ch...@rabobank.com>
> -------------------
> [ ] keep Java 1.5 compatibility: no good reason to upgrade.
> [ ] upgrade to Java 1.6: one step at a time.
> [X] upgrade to Java 1.7: new features are more important.
> -------------------
>
>
> Thanks.
>
> _____________________________________________________________
>
> This email (including any attachments to it) is confidential, legally
> privileged, subject to copyright and is sent for the personal attention of
> the intended recipient only. If you have received this email in error,
> please advise us immediately and delete it. You are notified that
> disclosing, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. Although we have taken
> reasonable precautions to ensure no viruses are present in this email, we
> cannot accept responsibility for any loss or damage arising from the
> viruses in this email or attachments. We exclude any liability for the
> content of this email, or for the consequences of any actions taken on the
> basis of the information provided in this email or its attachments, unless
> that information is subsequently confirmed in writing.
> _____________________________________________________________
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>
>
RE: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by "Kimpton, C (Chris)" <Ch...@rabobank.com>.
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[X] upgrade to Java 1.7: new features are more important.
-------------------
Thanks.
_____________________________________________________________
This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing.
_____________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org
Re: [POLL] Minimal JRE level as of HttpClient 4.4
Posted by "Chawla, Vanita" <vc...@umassp.edu>.
-------------------
[ ] keep Java 1.5 compatibility: no good reason to upgrade.
[ ] upgrade to Java 1.6: one step at a time.
[X] upgrade to Java 1.7: new features are more important.
-------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org<ma...@hc.apache.org>
For additional commands, e-mail: httpclient-users-help@hc.apache.org<ma...@hc.apache.org>