Annotation tests should not rely on JDK-specific toString() representation
Issue: SPR-14645
This commit is contained in:
parent
7a88776329
commit
faf6e5d8fa
|
|
@ -1357,11 +1357,6 @@ public class AnnotationUtilsTests {
|
||||||
assertNotNull(synthesizedWebMapping2);
|
assertNotNull(synthesizedWebMapping2);
|
||||||
|
|
||||||
assertThat(webMappingWithAliases.toString(), is(not(synthesizedWebMapping1.toString())));
|
assertThat(webMappingWithAliases.toString(), is(not(synthesizedWebMapping1.toString())));
|
||||||
|
|
||||||
// The unsynthesized annotation for handleMappedWithSamePathAndValueAttributes()
|
|
||||||
// should produce the same toString() results as synthesized annotations for
|
|
||||||
// handleMappedWithPathAttribute()
|
|
||||||
assertToStringForWebMappingWithPathAndValue(webMappingWithPathAndValue);
|
|
||||||
assertToStringForWebMappingWithPathAndValue(synthesizedWebMapping1);
|
assertToStringForWebMappingWithPathAndValue(synthesizedWebMapping1);
|
||||||
assertToStringForWebMappingWithPathAndValue(synthesizedWebMapping2);
|
assertToStringForWebMappingWithPathAndValue(synthesizedWebMapping2);
|
||||||
}
|
}
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue