Re: HttpClient 4.4 time line; Re: [POLL] Minimal JRE level as of HttpClient 4.4

[Daz DeBoer <da...@gradleware.com>]

Sorry I missed this poll.

I'm a developer of Gradle, and we use HttpClient pretty heavily under the
covers as part of our dependency resolution engine.
Unfortunately we're stuck with Java 1.5 compatibility for the time being:
that _may_ change to 1.6 for Gradle 2.0 (early next year), but it
definitely won't be 1.7 any time soon.

If you guys decide to upgrade then fair enough; I guess we'll need to
decide whether to backport new features, stick with what we've got or look
elsewhere. (We'd be quite interested in integrated Windows Authentication.)

Anyway, just another data point, not a vote either way.
cheers
Daz

On Tue, Sep 17, 2013 at 2:10 AM, Oleg Kalnichevski <ol...@apache.org> wrote:

> 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: HttpClient 4.4 time line; Re: [POLL] Minimal JRE level as of HttpClient 4.4

[Oleg Kalnichevski <ol...@apache.org>]

On Wed, 2013-10-09 at 15:25 -0600, Daz DeBoer wrote:
> Sorry I missed this poll.
> 
> I'm a developer of Gradle, and we use HttpClient pretty heavily under the
> covers as part of our dependency resolution engine.
> Unfortunately we're stuck with Java 1.5 compatibility for the time being:
> that _may_ change to 1.6 for Gradle 2.0 (early next year), but it
> definitely won't be 1.7 any time soon.
> 
> If you guys decide to upgrade then fair enough; I guess we'll need to
> decide whether to backport new features, stick with what we've got or look
> elsewhere. (We'd be quite interested in integrated Windows Authentication.)
> 
> Anyway, just another data point, not a vote either way.
> cheers
> Daz
> 

Hi Daz

No formal decision has been taken yet, however I think it is almost
certain we will no longer support Java 1.5 for HC 4.4 series. I also do
not think HttpClient should requite Java 1.7. This is more likely to
happen for HttpAsyncClient though due to NIO2. Upstream projects will be
consulted in any case. Regardless of what happens in HC 4.4 I can assure
you that HC 4.3 will be supported as long as Gradle depends on it (if
need be, simply out of my personal utter admiration for Gradle). 

Cheers

Oleg


---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org