Re: [Jython-dev] Updating extlibs

[Jim B. <jim...@py...>]

These changes look good to me. I will test out your patch, but all of this
is in line with similar updates we have made in the past, usually around
this time in the dev cycle.

I'm glad that moving to Gradle will make this re-pinning to upstream
dependencies much easier going forward!

On Mon, May 22, 2017 at 8:46 AM, Stefan Richthofer <Ste...@gm...
> wrote:

> I uploaded the mentioned updates to
> https://github.com/Stewori/jython.
> See detailed changes at
> https://github.com/Stewori/jython/commit/ee2b1263306f779bf8e9499afc6d02
> 267648ac36
>
> This might not yet work smoothly with Java 7, I will check and adjust that
> tomorrow.
> Some packages were built from source using Java 8 and I'm not sure whether
> the gradle
> scripts always configured Java 7 source compatibility properly.
> However if some people could test it, especially on OSX, would be nice.
>
> Best
>
> Stefan
>
>
> > Gesendet: Montag, 22. Mai 2017 um 04:07 Uhr
> > Von: "Stefan Richthofer" <Ste...@gm...>
> > An: "Jython Developers" <jyt...@li...>
> > Betreff: Updating extlibs
> >
> > Hey all,
> > I spent some effort to explore feasibility of updating extlibs,
> especially minor versions (but sometimes even major version, e.g. guava and
> icu4j).
> > My results so far, tested with regrtest on Linux and Windows 10 using
> Java8 ("okay" means I did not observe additional regrtest failures):
> >
> > ASM 5.0.4             -> 5.2     okay
> > bouncycastle:
> > bcpkix-jdk15on-1.54   -> 1.57    okay
> > bcprov-jdk15on-1.54   -> 1.57    okay
> >
> > commons-compress-1.12 -> 1.14    okay
> > guava-20.0            -> 22.0rc1 okay
> > icu4j-58.1            -> 59_1    okay
> > Netty 4.1.6           -> 4.1.11  okay
> > java-sizeof-0.0.5     -- still current
> > jffi-1.2.13           -> 1.2.15  okay
> > jnr-ffi-2.1.0         -> 2.1.5   okay
> > jnr-netdb-1.1.6       -- still current
> > jnr-posix-3.0.31      -> 3.0.41  okay
> > jnr-constants-0.9.5   -> 0.9.9   okay
> > New platforms: jffi-aarch64-Linux.jar, jffi-ppc64le-Linux.jar, can be
> added...?
> > Updated various other changed platform specific jars to jffi-1.2.15
> (okay as far as tested)
> > xercesImpl-2.11.0          -- still current
> > jline-2.14.2               -> 2.14.3      okay (didn't try jline-3 this
> time)
> > jarjar-1.4                 -- still current
> > mysql-connector-java-5.1.6 -> 5.1.42      okay
> > postgresql-8.3-603.jdbc4   -> 42.1.1-jre7 okay
> >
> > ----------These failed, so leaving them as it is:
> > Antlr 3.1.3                -> 3.5.2  fails
> > junit-4.10                 -> 4.12 or 4.11 class file for
> org.hamcrest.Matcher not found
> > (staying with 4.10 for now to avoid new dependency on hamcrest-matcher)
> > javax.servlet-api-2.5      -> 3.1.0  fails
> > mockrunner      (better don't touch; whole structure changed)
> > cpptasks        (better don't touch)
> >
> > - will be able to test with Java 7 on Tuesday, because I left my old
> laptop in the office.
> > - will upload a fork containing these updates. Would be good if someone
> else could also test, especially on OSX.
> > Maybe some stuff was not covered by regrtests. However the chance that
> updates solve issues and that they create issues are probably somewhat
> equal and I'd prefer to focus on fixing issues with current versions rather
> than older ones.
> > So I'm strongly for getting this in if regrtests go through on Java 7
> and OSX. 2.7.1RC-phase will be a good opportunity to confirm workability of
> these updates. Any concerns?
> >
> > -Stefan
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jython-dev mailing list
> Jyt...@li...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>