Is it common to find calls to ClassNode#getTypeClass in Grails, GORM, etc.? Or is it happening at just a few locations? I ask because ClassNode#isResolved is not a proper guard for ClassNode#getTypeClass and they could be wrapping getTypeClass in try/catch. Even if Groovy provided a safer alternative to isResolved, the code that uses getTypeClass would need to use the new method, so you'd be required to find all the same places and you'd need to manage backwards compatibility.
From: Paolo Di Tommaso <paolo.ditomm...@gmail.com> Sent: Thursday, July 2, 2020 1:02 AM To: dev@groovy.apache.org; Paul King <pa...@asert.com.au> Subject: Re: next releases This issue causes a horrible experience with IntelliJ and groovy code annotated for bytecode generation with (e.g. Grails GORM, Micronaut, etc). https://issues.apache.org/jira/projects/GROOVY/issues/GROOVY-9209<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fprojects%2FGROOVY%2Fissues%2FGROOVY-9209&data=02%7C01%7Ceric.milles%40thomsonreuters.com%7C35c14db7e7694d135d4708d81e4d9867%7C62ccb8646a1a4b5d8e1c397dec1a8258%7C0%7C0%7C637292665899311260&sdata=rX0rk1QteAANAiXVXNRp4SiVNlyVkJwW%2BBjsAM%2FTAe0%3D&reserved=0> 🙏 On Thu, Jul 2, 2020 at 12:41 AM Paul King <pa...@asert.com.au<mailto:pa...@asert.com.au>> wrote: Hi everyone, I'd like to do another 2.5 and 3 release late this week or early next week. Time to work on any bug fixes that you want included or let me know if the timing doesn't work. Thanks, Paul.
