1. 27 4月, 2021 2 次提交
  2. 26 4月, 2021 1 次提交
  3. 23 4月, 2021 3 次提交
  4. 22 4月, 2021 6 次提交
  5. 21 4月, 2021 11 次提交
  6. 20 4月, 2021 1 次提交
  7. 18 4月, 2021 1 次提交
    • S
      Ensure @DateTimeFormat tests pass on Java 9+ · e489706f
      Sam Brannen 提交于
      Prior to this commit, two tests for exception handling regarding
      @DateTimeFormat processing only passed on Java 8. This is due to the
      fact that the toString() implementation for annotations changed in Java
      9. Specifically, the representation for arrays changed from [] to {},
      and strings are enclosed in double quotes beginning with Java 9.
      
      This commit ensures that the affected @DateTimeFormat tests pass on
      Java 9+, by making the assertions more lenient regarding toString()
      output for annotations.
      
      See gh-26777
      See gh-26804
      e489706f
  8. 17 4月, 2021 2 次提交
    • R
      HandlerMappingIntrospector ensures initialized RequestPath · 69bbdce8
      Rossen Stoyanchev 提交于
      Closes gh-26814
      69bbdce8
    • S
      Retain root cause for parsing patterns in @DateTimeFormat · 0f31830a
      Sam Brannen 提交于
      The support for fallback parsing patterns in @DateTimeFormat introduced
      in gh-20292 introduced a regression in that the original cause of the
      parsing exception was no longer retained.
      
      gh-26777 addressed that regression for `java.time` support; whereas,
      this commit addresses that regression for legacy Date types.
      
      This commit ensures that the original ParseException is set as the
      cause for any newly created ParseException, thereby retaining the
      original exception as the root cause.
      
      Closes gh-26804
      0f31830a
  9. 16 4月, 2021 3 次提交
  10. 15 4月, 2021 5 次提交
  11. 14 4月, 2021 1 次提交
  12. 13 4月, 2021 4 次提交