spring-framework

Spring Framework

Sam Brannen db4d51ba32 Remove unused type parameter declarations in XpathRequestMatchers Prior to this commit, several of the methods in XpathRequestMatchers declared unused type parameters (e.g., <T>). This was obviously the result of copying an existing method that actually needs the type parameter for proper casting. For example, the following ... public <T> RequestMatcher exists() { // ... } ... should actually be declared without <T>, since T is not used in the implementation or in the return type: public RequestMatcher exists() { // ... } This commit removes all unused type parameter declarations in XpathRequestMatchers. Side Effects: Now that we have removed the unused type parameter declarations, users will see the following side effects if they had previously declared a type argument when invoking such methods. - Java: an "Unused type arguments for the non generic method ..." warning will be generated by the compiler, but the code will continue to work unmodified. - Kotlin: a "Type inference failed: Not enough information to infer parameter T in fun ..." compiler error will be raised, causing the code to no longer compile (see https://youtrack.jetbrains.com/issue/KT-5464). Removal of the type argument declaration will allow the code to work correctly again. Closes gh-23860		6 years ago
..
src	Remove unused type parameter declarations in XpathRequestMatchers	6 years ago
.springBeans	…
spring-test.gradle	Upgrade to SLF4J 1.7.28, Groovy 2.5.8, RxJava 2.2.12, Joda-Time 2.10.4, Rome 1.12.2, OkHttp 3.14.3, Apache HttpClient 4.5.10, Apache Johnzon 1.1.13	6 years ago