Chris Vest b3d3269b8c Avoid overspecifying ScheduledFuture when Future will do (#11636) ... Motivation: Overspecifying interfaces can increase coupling and make refactoring harder down the line. Modification: Places that were specifying fields, variables, and return types as ScheduledFuture, but did not use any features specific to ScheduledFuture, have been changed to specify Future instead. Result: Cleaner code.		2021-08-31 16:05:21 +02:00
..
main/java/io/netty/handler/proxy	Avoid overspecifying ScheduledFuture when Future will do (#11636)	2021-08-31 16:05:21 +02:00
test/java/io/netty/handler/proxy	Migrate handler-proxy tests to JUnit 5 (#11313)	2021-05-26 10:37:18 +02:00