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-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
