Hi, does <https://github.com/apache/grails-core/pu...
# questions
l
Hi, does https://github.com/apache/grails-core/pull/15187 mean that Grails 7 doesn't supporto depending on a micronaut lib based on netty http client ?
t
Essentially, yes. As a workaround, you can downgrade the Micronaut platform version, specified in
gradle.properties
, from 4.9.2 to 4.7.6 which is compatible with Netty 4.1.x. https://github.com/apache/grails-core/issues/15149#issuecomment-3433579388
j
downgrading won't work because there was a bug fix for groovy 4 in later versions. Spring is expected to update netty soon - my hope was in the release that's tomorrow
👍 1
we intend to update to spring rather quickly (within a week) - so if it does include the upgrade, it will be easy to pick it up
l
Hi, I'm guessing netty dependency mismatch will stay for the whole grails 7.x, but is there a perspective for grails8? Sorry I'm not really keeping up to date, only have a few days per year maintaining a grails 6 app. Use case is having a (fairly complex ) web client to use in small micronaut apps, clis and a grails app.
j
Unfortunately, it's spring that's decided that. It will be bumped in Spring Boot 4 (Grails 8 ). I would strongly urge you to open a ticket on the micronaut spring repo since that's what we use. They have to solve this b/c we can't.
l
Having trouble making an informed decision for a web client easy to integrate to those while having as few deps CVEs as possible
j
The RestClient from spring is basically micronaut if you include the HttpExchange starter. it's almost a drop in replacement with minor renames. It's shockingly easy
That's what we ended up switching to.
spring lets you "choose" which http client you use under their abstraction too
so you aren't forced to use netty, you can use many other options