-
Notifications
You must be signed in to change notification settings - Fork 168
[JENKINS-65237] Bump Groovy from 2.4.12 to 2.4.21 #373
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
Conversation
Co-authored-by: Jesse Glick <[email protected]>
Co-authored-by: Jesse Glick <[email protected]>
Yeah, I'm not in any rush for this to be merged. I just wanted to file the PR to close the loop on remaining tasks regarding the Groovy upgrade. |
Heyo @basil, do you look forward to merge this PR anytime soon? See my PR linked, it would depend on the baseline bump you look forward to do. |
I am not a maintainer, but perhaps @car-roll could consider merging this now that we have an additional use case in mind. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will merge once @timja 's comment is addressed
Co-authored-by: Jesse Glick <[email protected]>
BTW my general preference is for all of my PRs to be squash-merged to keep the history clean, but I recognize that others have different preferences. I do not feel strongly about this, and ultimately the decision is up to the maintainer. |
Adapting to jenkinsci/jenkins#5939, specifically this comment:
The change to
GroovyCallSiteSelectorTest
adapts a test that was using a Guava class that was removed in the latest version of Guava, which is now present in core. I resolved this issue by replacing the usage with the equivalent class from Apache Commons IO.