Chris Vest edf4e28afa Change !future.isSuccess() to future.isFailed() where it makes sense (#11616) ... Motivation: The expression "not is success" can mean that either the future failed, or it has not yet completed. However, many places where such an expression is used is expecting the future to have completed. Specifically, they are expecting to be able to call `cause()` on the future. It is both more correct, and semantically clearer, to call `isFailed()` instead of `!isSuccess()`. Modification: Change all places that used `!isSuccess()` to mean that the future had failed, to use `isFailed()`. A few places are relying on `isSuccess()` returning `false` for _incomplete_ futures, and these places have been left unchanged. Result: Clearer code, with potentially fewer latent bugs.		2021-08-26 09:43:17 +02:00
..
src/main/java/io/netty/testsuite	Change !future.isSuccess() to future.isFailed() where it makes sense (#11616)	2021-08-26 09:43:17 +02:00
.gitignore	updated udt and connection test	2013-05-14 06:46:07 +02:00
pom.xml	Use the standard japicmp.skip instead of the custom skipJapicmp (#11558)	2021-08-10 09:07:04 +02:00