jdaugherty commented on issue #972: URL: https://github.com/apache/grails-doc/issues/972#issuecomment-2848666150
I don't think it's a hard dependency, but the work hasn't been done to investigate it. Yes, there is a workaround, but the goal of choosing a default JDK is to not have people use workarounds. I suspect the date formatting issues are minor / not disruptive, but I haven't had time to investigate it - hence why I'm hesitant to recommend 21 as the default. We welcome any help on this issue: If you have time to look into the ticket & the associated spring documentation, it would be helpful. There are tests in grails-core that were "fixed" by selectively running on jdk versions. They need reviewed at a minimum in addition to the ticket + associated spring documentation. Our main focus is getting 7.0 released right now, and until that's done I don't think we want to expand the scope by changing the recommend default JDK. We had several last minute requirements due to the ASF merge and it's consuming almost all of the development time to get an ASF release done. Due to the limited resource, I'd suggest we leave it at 17 for now. We do test in parallel with Linux / Mac / Windows across JDK 17, 21, & 23 now - so we know that the impacts of JDK 21 will be limited; likely just this date issue. On the horizon, we'll have a more regular release cycle after 7. We'll effectively mirror Spring's. One of the main goals of the mono repo merge was to accelerate releases so we don't have a huge effort on updating dependencies in the future. So while Grails 7 will release after a significant development time, Grails 8 will likely come within the year. We can recommend JDK 21 at that time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
