Re: [Jython-dev] Java 7 or 8?
Stefan Richthofer <[email protected]> Sat, 27 Jul 2019 14:01:26 +0200
| Newsgroups | gmane.comp.lang.jython.user,gmane.comp.lang.jython.devel |
|---|---|
| Message-ID | <CACQYzFKAhL0GRd+9bkMeLnL4aUqzfJo9VN2RFgiFcVf9F5CNOA@mail.gmail.com> |
--===============0685789334630485398== Content-Type: multipart/alternative; boundary="00000000000061d1a8058ea86d8e" --00000000000061d1a8058ea86d8e Content-Type: text/plain; charset="UTF-8" AFAIK, the current Jython 2.7 master still compiles and runs with Java 7. So why would we drop that support right now? At least I think we shouldn't explicitly/on purpose destroy Java 7 compatibility e.g. by inserting a lambda or so somewhere. Dropping Java 7 support just "one second" before 2.7.2 release looks rushed to me. IMO the right moment to drop support for something is right after a release not in the last moment before a release. It's usually good practice to have a designated last release to support something. For 2.7.2 it was decided some time ago that it would be that last release to support Java 7 IIRC. I personally know a company where still Java 6 is floating around and I suspect there are plenty. So the EOL argument is more a virtual one. Anyway, I'm not fanatic for Java 7, it just appears to be a low-hanging fruit to keep the compatibility just on these last meters till the release. And all the named reasons sum up for me to vote for Java 7 support in 2.7.2. At least, let's make Java 7 support "on best effort", i.e. avoid to break it explicitly, and Java 8 can be the official support. That's my view. Best Stefan Am Sa., 27. Juli 2019 um 01:48 Uhr schrieb Jim Baker <[email protected]>: > Previously we resolved this issue based on what version of Java is > publicly and currently supported. Given Java 7 was end of lifed a few years > ago, and these problems, it makes sense to require Java 8 (or 11, for > similar reasons). > > On Fri, Jul 26, 2019, 1:54 PM Jeff Allen <[email protected]> wrote: > >> When the project set out to create Jython 2.7.2, it was reasonable still >> to support Java 7. Now we find ourselves on the verge of a 2.7.2 beta >> release, Java 8 seems the logical minimum. We currently build and test >> on Java 7 but some things would resolve themselves if we could move on. >> We intend to support "before and after Jigsaw" JVMs (say 8 and 11). >> >> Straw poll: does anyone amongst our users have a good reason why Jython >> 2.7.2 should run on Java 7? >> >> -- >> Jeff Allen >> >> >> >> _______________________________________________ >> Jython-dev mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> > _______________________________________________ > Jython-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jython-users > --00000000000061d1a8058ea86d8e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>AFAIK, the current Jython 2.7 master still compiles a= nd runs with Java 7. So why would we drop that support right now?</div><div= >At least I think we shouldn't explicitly/on purpose destroy Java 7 com= patibility e.g. by inserting a lambda or so somewhere.</div><div>Dropping J= ava 7 support just "one second" before 2.7.2 release looks rushed= to me. IMO the right moment to drop support</div><div>for something is rig= ht after a release not in the last moment before a release. It's usuall= y good practice to have a designated</div><div>last release to support some= thing. For 2.7.2 it was decided some time ago that it would be that last re= lease to support Java 7</div><div>IIRC. I personally know a company where s= till Java 6 is floating around and I suspect there are plenty. So the EOL a= rgument</div><div>is more a virtual one. Anyway, I'm not fanatic for Ja= va 7, it just appears to be a low-hanging fruit to keep the compatibility j= ust</div><div>on these last meters till the release. And all the named reas= ons sum up for me to vote for Java 7 support in 2.7.2. At least,</div><div>= let's make Java 7 support "on best effort", i.e. avoid to bre= ak it explicitly, and Java 8 can be the official support. That's my vie= w.</div><div><br></div><div>Best</div><div><br></div><div>Stefan<br></div><= /div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">A= m Sa., 27. Juli 2019 um 01:48=C2=A0Uhr schrieb Jim Baker <<a href=3D"mai= lto:[email protected]">[email protected]</a>>:<br></div><blockquot= e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s= olid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">Previously we res= olved this=C2=A0issue based on what version of Java is publicly and current= ly supported. Given Java 7 was end of lifed a few years ago, and these prob= lems, it makes sense to require Java 8 (or 11, for similar reasons).</div><= br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri,= Jul 26, 2019, 1:54 PM Jeff Allen <<a href=3D"mailto:[email protected]"= rel=3D"noreferrer" target=3D"_blank">[email protected]</a>> wrote:<br>= </div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b= order-left:1px solid rgb(204,204,204);padding-left:1ex">When the project se= t out to create Jython 2.7.2, it was reasonable still <br> to support Java 7. Now we find ourselves on the verge of a 2.7.2 beta <br> release, Java 8 seems the logical minimum. We currently build and test <br> on Java 7 but some things would resolve themselves if we could move on. <br= > We intend to support "before and after Jigsaw" JVMs (say 8 and 11= ).<br> <br> Straw poll: does anyone amongst our users have a good reason why Jython <br= > 2.7.2 should run on Java 7?<br> <br> -- <br> Jeff Allen<br> <br> <br> <br> _______________________________________________<br> Jython-dev mailing list<br> <a href=3D"mailto:[email protected]" rel=3D"noreferrer noref= errer" target=3D"_blank">[email protected]</a><br> <a href=3D"https://lists.sourceforge.net/lists/listinfo/jython-dev" rel=3D"= noreferrer noreferrer noreferrer" target=3D"_blank">https://lists.sourcefor= ge.net/lists/listinfo/jython-dev</a><br> </blockquote></div> _______________________________________________<br> Jython-users mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">Jyt= [email protected]</a><br> <a href=3D"https://lists.sourceforge.net/lists/listinfo/jython-users" rel= =3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/listi= nfo/jython-users</a><br> </blockquote></div> --00000000000061d1a8058ea86d8e-- --===============0685789334630485398== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============0685789334630485398== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Jython-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jython-users --===============0685789334630485398==--