Re: The comment "pin to ASM something until we upgrade compilation"

Right before Jython 2.7.1 release I went through all dependencies and
upgraded each to the highest version that didn't break anything. I vaguely
remember that ams couldn't be upgraded further at that time but don't
remember what went broken. Maybe it was fixed as a by product of some work
done since then. However, better test carefully, also on other platforms
etc.

Am Do., 22. Nov. 2018, 17:50 hat Jeff Allen <[email protected]>
geschrieben:

> In build.xml at a couple of points we find the comment:
>
> <!-- pin to ASM 5.2 until we upgrade compilation -->
>
> In fact we have "pinned" ASM at 5.0.3, then 5.0.4 and then 5.2. I need
> to advance ASM, probably to 7.0, to fix
> http://bugs.jython.org/issue2362, and it seems to work (passes regrtest
> -e on Windows). Does anyone know why we chose to pin ASM at 5?
>
> --
>
> Jeff Allen
>
>
>
> _______________________________________________
> Jython-dev mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>

_______________________________________________
Jython-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-dev