Re: [Jython-dev] Java 7 or 8?

--===============1262510630988454867==
Content-Type: multipart/alternative; boundary="0000000000005b473605917eae51"

--0000000000005b473605917eae51
Content-Type: text/plain; charset="UTF-8"

+100

I like this well-considered compromise. Source compatibility with Java 7
ensures it is possible for a self service model if there are users who
actually need Java 7. Meanwhile we are able to ensure all of our
dependencies are supported, which is key for any release.

This approach also gives an immediate path forward to being on Java 11, the
only current LTS option, for a Jython 2.7.3, as well as setting up for
Jython 3.x development.

- Jim


On Sun, Sep 1, 2019 at 4:11 AM Jeff Allen <[email protected]> wrote:

> It is a fact that we remain source-compatible with Java 7. We test on 7,
> 8 and 11 in the CI.
>
> Java 7 is past EOL, and no-one should really be using it in production,
> but a few may still be running Jython on it. (No-one has said they are,
> so it's at best a reasonable conjecture.) I have observed test failures
> with SSL on Java 7, that disappear on Java 8, since upgrading the BC
> jars to satisfy security concerns.
>
> I propose we compile releases up to 2.7.2 final with Java 8, and for the
> Java 8 target. (It really doesn't seem right to compile it with an
> unsupported Java 7.) This means the Jython that users download will
> require a minimum of Java 8 to run. We support up to Java 11, with
> reasonable confidence beyond that.
>
> But we remain source-compatible with Java 7 up to 2.7.2 final. Then, if
> a user really needs a version that runs on Java 7, we can show them how
> to build one. I believe it is a matter of defining properties in or
> around the Ant build, down-grading the BC JARs if need be, and making a
> snapshot installer. It will be an "unofficial" build that we do not
> undertake to support, and comes with a number of (additional) known
> defects.
>
> Good compromise?
>
> Jeff
>
> Jeff Allen
>
> On 26/07/2019 21:54, Jeff Allen 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?
> >
>
>
> _______________________________________________
> Jython-dev mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>

--0000000000005b473605917eae51
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>+100<br><br>I like this well-considered compromise. S=
ource compatibility with Java 7 ensures it is possible for a self service m=
odel if there are users who actually need Java 7. Meanwhile we are able to =
ensure all of our dependencies are supported, which is key for any release.=
</div><div><br></div><div>This approach also gives an immediate path forwar=
d to being on Java 11, the only current LTS option, for a Jython 2.7.3, as =
well as setting up for Jython 3.x development.</div><div><br></div><div>- J=
im</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr=
" class=3D"gmail_attr">On Sun, Sep 1, 2019 at 4:11 AM Jeff Allen &lt;<a hre=
f=3D"mailto:[email protected]">[email protected]</a>&gt; wrote:<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">It is a fact that we rema=
in source-compatible with Java 7. We test on 7, <br>
8 and 11 in the CI.<br>
<br>
Java 7 is past EOL, and no-one should really be using it in production, <br=
>
but a few may still be running Jython on it. (No-one has said they are, <br=
>
so it&#39;s at best a reasonable conjecture.) I have observed test failures=
 <br>
with SSL on Java 7, that disappear on Java 8, since upgrading the BC <br>
jars to satisfy security concerns.<br>
<br>
I propose we compile releases up to 2.7.2 final with Java 8, and for the <b=
r>
Java 8 target. (It really doesn&#39;t seem right to compile it with an <br>
unsupported Java 7.) This means the Jython that users download will <br>
require a minimum of Java 8 to run. We support up to Java 11, with <br>
reasonable confidence beyond that.<br>
<br>
But we remain source-compatible with Java 7 up to 2.7.2 final. Then, if <br=
>
a user really needs a version that runs on Java 7, we can show them how <br=
>
to build one. I believe it is a matter of defining properties in or <br>
around the Ant build, down-grading the BC JARs if need be, and making a <br=
>
snapshot installer. It will be an &quot;unofficial&quot; build that we do n=
ot <br>
undertake to support, and comes with a number of (additional) known defects=
.<br>
<br>
Good compromise?<br>
<br>
Jeff<br>
<br>
Jeff Allen<br>
<br>
On 26/07/2019 21:54, Jeff Allen wrote:<br>
&gt; When the project set out to create Jython 2.7.2, it was reasonable <br=
>
&gt; still to support Java 7. Now we find ourselves on the verge of a 2.7.2=
 <br>
&gt; beta release, Java 8 seems the logical minimum. We currently build and=
 <br>
&gt; test on Java 7 but some things would resolve themselves if we could <b=
r>
&gt; move on. We intend to support &quot;before and after Jigsaw&quot; JVMs=
 (say 8 <br>
&gt; and 11).<br>
&gt;<br>
&gt; Straw poll: does anyone amongst our users have a good reason why <br>
&gt; Jython 2.7.2 should run on Java 7?<br>
&gt;<br>
<br>
<br>
_______________________________________________<br>
Jython-dev mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">Jytho=
[email protected]</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/jython-dev" rel=3D"=
noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/=
jython-dev</a><br>
</blockquote></div>

--0000000000005b473605917eae51--


--===============1262510630988454867==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============1262510630988454867==
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

--===============1262510630988454867==--