Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(upgrade): Upgrade to Grails 5, Increase compatible with Apache Groovy 4 #17

Merged
merged 10 commits into from
Feb 22, 2024

Conversation

matrei
Copy link
Contributor

@matrei matrei commented Feb 21, 2024

The main objective of this PR is to make it compatible with Groovy 4.

  • Update to Grails 5
  • Add Github workflows
  • Add Dependabot and Renovate
  • Remove dependency on methods using java.util.XmlSlurper in SpringIOUtils
  • Fix tests assertions

BREAKING CHANGE: Java 8, Groovy 3
This removes the dependency on the SpringIOUtils class from
grails-bootstrap. Use classes from groovy.xml.* instead of
groovy.util.* which allows for updating to Groovy 4 in
dependent projects, for example Grails itself.

This commit can optionally be reversed after this project has
updated to a Grails version where SpringIOUtils has also
migrated to the Groovy 4 compatible classes.
The test was expecting JSON properties to be in a certain order.
This change removes that expectation.
@puneetbehl puneetbehl changed the base branch from master to 5.0.x February 22, 2024 19:02
@puneetbehl puneetbehl merged commit a887a65 into grails:5.0.x Feb 22, 2024
@matrei matrei deleted the matrei/branch-5.0.x branch February 22, 2024 21:35
@puneetbehl puneetbehl changed the title Branch 5.0.x Upgrade to Grails 5, Increase compatible with Apache Groovy 4 Feb 25, 2024
@puneetbehl puneetbehl changed the title Upgrade to Grails 5, Increase compatible with Apache Groovy 4 feat(upgrade): Upgrade to Grails 5, Increase compatible with Apache Groovy 4 Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants