You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you guys have a release in mind where you would drop 1.6 support? Unfortunately my team will be stuck on 1.6 for awhile longer so just wondering when this might become an issue for us. Thanks
Do you guys have a release in mind where you would drop 1.6 support? Unfortunately my team will be stuck on 1.6 for awhile longer so just wondering when this might become an issue for us. Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Yes, Closeable could also work (it's actually implemented by Connection), but it wouldn't for Channel. This issue is more of a reminder to see what we can do regarding auto-closeable resources (mainly Connection and Channel, but there may other places where it could be appropriate) when we drop Java 1.6 support.
When we drop Java 1.6 compliance.
The text was updated successfully, but these errors were encountered: