This message was deleted.
# questions
s
This message was deleted.
g
Is this official efforts or only for your own pilot project? If this is the first case, I will really be excited, if this is the later case, why dont you make your efforts align with the official release as this is such an smaller size community. I do think they need help as well
p
Thanks for the response. I too would be interested to know if the wider Grails community could make use of this work.
g
I’d love to see you effort merged in the main grails project so that anyone can take advantage of it.
m
@gaolei No one wants to struggle with a framework because it seems crazy and potentially costly, the only reason being that the framework doesn't fulfill the developer's needs and the maintainer can't deliver. In most cases, the better choice is to go with another framework that is better and more suitable. The reason I fork Grails and then spend a lot of time modifying it myself is that, yes, it seems very hard to understand. At first it was to fix bugs, then because of some new features I could only modify the framework code.
Like everyone else, all I know is that Grails 7 will support Spring 3, but I don't know any more details, and I've asked on Twitter and GitHub for a roadmap for the next version of Grails, and the development team hasn't responded yet. The repository doesn't have a 7.0.x branch either. I think it's not too difficult to upgrade to Spring 3 and migrate to Jakarta EE, while upgrading to Groovy 4 and Hibernate 6 will be a bit more complicated.
g
I respect and I understand where you are and where you started. For me, as I mentioned to other members here, only thing I can contribute is to convince my customers apply this framework to their projects. By far, grails gave me the strength and flexibilities to fulfill my contract.
I just hope everybody can put their efforts together to make things better. If this project goes to end, I surely can switch to use spring boot and other things, but that way we will have to live in a less beautiful world. Please continue your great work
m
As you say, in a sense, we are all customers of open source projects, i.e. users as well as developers and contributors, developing projects using frameworks and libraries, submitting problem reports, participating in problem discussions, posting and sharing via social, contributing code and updating documentation.
I ended up deleting the development branch at the end of November last year for posting some of my work on Twitter that involved the "Grails" trademark. I'm thinking about opening the source of GoBoots (forked Grails 5.1) again, but of course I'll ask the current owners of Grails for permission first. Because in addition to upgrading to Spring Boot 3 and Groovy 4, there are also a lot of new features that others can learn if they are interested.
šŸ‘ 1
šŸ™ 2
Let's make it happen! Good luck to me, thank you! https://twitter.com/rainboyan/status/1727506003590295907
Spring Boot 3.2 has been released, 2.7.x and 3.0.x have been the end of OSS support. https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-3.2-Release-Notes
It will be available in GitHub šŸ€