On Fri, 2013-09-20 at 21:28 +0100, sebb wrote: > On 16 September 2013 13:02, Oleg Kalnichevski <[email protected]> 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: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
