-
Notifications
You must be signed in to change notification settings - Fork 7
Require Java 25 #7305
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
base: develop
Are you sure you want to change the base?
Require Java 25 #7305
Conversation
|
@labkey-jeckels there are a couple other places that should be updated ( |
Updated. I also eliminated |
labkey-susanh
left a comment
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.
I think I'm not fully understanding how the ConnectionState and Cleaner work since JavaDocs say the state should have no reference to the object being cleaned, but then I'm not sure how it can be used to clean anything.
In any case, I think the || true hacks want removing.
| private final StackTraceElement[] _debugCreated; | ||
| private final @Nullable DbScope _scope; | ||
| private final @Nullable Connection _connection; | ||
| private final ResultSet _rs; // This is the underlying result set |
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.
Is this OK? I thought the state was not supposed to have a reference to the object being cleaned?
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.
I think we're OK. The ResultSetImpl is the thing being cleaned. This member variable is the ResultSet that's being wrapped. See the use of rs in the call to the ResultSetState constructor vs this being passed to the cleaner on the next line.
These can be confusing and easy to mess up, so let me know what you think of my explanation.
Rationale
We're upgrading to require Java 25.
Changes