@marwand has agreed to do this. @marwand if you’d like assistance or to split up the work, let @f.karim @kieuanhvu @newmannhu @rahulnama @shahbaz @zhangwei know.
Biggest thing here is to ensure that we’re using secure versions that are recent and function with Moqui.
The plan is to start off with updating moqui-framework and moqui-runtime, and then move to the other components.
@marwand when you’ve got working versions, maybe you can ask others here to test.
Let’s use: GitHub - moqui/moqui-framework at upgrade-libs for the branch.
Note that this doesn’t include upgrading:
- groovy
- jetty
- java ee to jakarta ee
2 Likes
Thank you guys for the assistance offer, I believe I can get this done quickly within the next few days, I’ll let you know if I get stuck somewhere. Help with testing would be appreciated. Thanks!
1 Like
Forgot to ask, about not updating groovy, I’m assuming you mean not to upgrade to V4?
I’m asking because there is a new patch version [3.0.19 → 3.0.24], I believe it shouldn’t break anything. What do you think?
– Update
I created a pull request for the upgrades: Upgrade Dependencies by marwand · Pull Request #658 · moqui/moqui-framework · GitHub
I described the changes in the pull request, I would appreciate if any of you guys could test & let me know if you run into any issues.