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