On 11.11.19 12:35, Andres Almiray wrote:
Hello there,
I spoke with Rémi Forax at Devoxx justa few days ago regarding a
message sent to the Openjdk dev list related to Groovy/Gradle/ASM. Long
story short the toolchain is not updated because Groovy does not publish
a release with the latest ASM, which makes really hard to build projects
with latest OpenJDK early access builds because Gradle croaks.
A couple of ideas:
- push a Groovy release where the only change is an upgrade to latest
ASM release. In this way the Gradle team can test if any regressions
occur _only_ by ASM and not because we added something extra.
- stop shading ASM and use it as a regular dependency. Apparently we
used to shade ASM for valid reasons in the past, but now that we publish
Groovy as a BOM we may rely on regular dependencies.
I'm aware that any of these two changes do not constitute a change one
usually push during an RC cycle.
2.5 is on ASM 7.1, newest version is 7.2? I think that kind of update is
still a possibility. Paul? Daniel? Considering GROOVY-9271 I wonder
actually we did not go to 7.2 right away for 2.4...
The reason we shade Groovy is because many libraries use ASM and not all
version of ASM are compatible with each other. With the module system I
actually see more reasons to shade than less.
We could think to offer a version that uses the shaded ASM coming with
the JDK itself... though... not as easy with the module system?
Not wanting to push away responsibility, but there would also be the
possibility to replace the ASM lib within Groovy by the build process
Gradle uses.
bye blackdrag
