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 w
Many of those won't merge cleanly - I had tried a few already but I'll see
what can be done.
On Tue, Nov 12, 2019 at 1:35 AM Milles, Eric (TR Tech, Content & Ops) <
eric.mil...@thomsonreuters.com> wrote:
> I know this seems like a lot to ask for 2.5.9, but I scanned the commits
> in master and th
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,
Hi Jochen,
> 2.5 is on ASM 7.1, newest version is 7.2? I think that kind of update is
> still a possibility. Paul? Daniel?
Yep :-)
> Considering GROOVY-9271 I wonder
> actually we did not go to 7.2 right away for 2.4...
Upgrading to 7.X from 6.X is a big change. Frankly I am not sure
Here is the PR "GROOVY-9262: Bump asm to 7.2":
https://github.com/apache/groovy/pull/1081
Cheers,
Daniel.Sun
-
Apache Groovy committer & PMC member
Blog: http://blog.sunlan.me
Twitter: @daniel_sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
Just saying that using external ASM is an option now. Back then we had to
repackage because ASM wasn't backwards compatible so triggered all sorts of
problems when another library used it with a different version.
This is not the case now since you always pass in the ASM version in the
constructor
