1. 23 3月, 2019 1 次提交
  2. 22 3月, 2019 1 次提交
  3. 16 2月, 2019 1 次提交
  4. 10 9月, 2018 1 次提交
  5. 28 6月, 2018 1 次提交
  6. 27 3月, 2018 1 次提交
  7. 17 8月, 2017 1 次提交
  8. 19 7月, 2017 1 次提交
    • S
      Make getters and setters null-safety consistent · fb4ddb07
      Sebastien Deleuze 提交于
      This commit ensure that null-safety is consistent between
      getters and setters in order to be able to provide beans
      with properties with a common type when type safety is
      taken in account like with Kotlin.
      
      It also add a few missing property level @Nullable
      annotations.
      
      Issue: SPR-15792
      fb4ddb07
  9. 12 6月, 2017 2 次提交
  10. 09 6月, 2017 1 次提交
    • J
      Consistent use of @Nullable in spring-test · fd53d2a5
      Juergen Hoeller 提交于
      This commit also removes nullability from two common spots: ResolvableType.getType() and TargetSource.getTarget(), both of which are never effectively null with any regular implementation. For such scenarios, a non-null empty type/target is the cleaner contract.
      
      Issue: SPR-15540
      fd53d2a5
  11. 07 6月, 2017 1 次提交
    • J
      Consistent use of @Nullable across the codebase (even for internals) · f813712f
      Juergen Hoeller 提交于
      Beyond just formally declaring the current behavior, this revision actually enforces non-null behavior in selected signatures now, not tolerating null values anymore when not explicitly documented. It also changes some utility methods with historic null-in/null-out tolerance towards enforced non-null return values, making them a proper citizen in non-null assignments.
      
      Some issues are left as to-do: in particular a thorough revision of spring-test, and a few tests with unclear failures (ignored as "TODO: NULLABLE") to be sorted out in a follow-up commit.
      
      Issue: SPR-15540
      f813712f
  12. 01 6月, 2017 1 次提交
  13. 28 4月, 2017 2 次提交
  14. 30 1月, 2017 1 次提交
  15. 24 12月, 2016 1 次提交
  16. 05 7月, 2016 1 次提交
  17. 07 7月, 2015 1 次提交
  18. 14 5月, 2013 1 次提交
  19. 02 1月, 2013 1 次提交
  20. 29 12月, 2012 2 次提交
  21. 31 1月, 2012 1 次提交
    • C
      Rename modules {org.springframework.*=>spring-*} · 02a4473c
      Chris Beams 提交于
      This renaming more intuitively expresses the relationship between
      subprojects and the JAR artifacts they produce.
      
      Tracking history across these renames is possible, but it requires
      use of the --follow flag to `git log`, for example
      
          $ git log spring-aop/src/main/java/org/springframework/aop/Advisor.java
      
      will show history up until the renaming event, where
      
          $ git log --follow spring-aop/src/main/java/org/springframework/aop/Advisor.java
      
      will show history for all changes to the file, before and after the
      renaming.
      
      See http://chrisbeams.com/git-diff-across-renamed-directories
      02a4473c
  22. 26 1月, 2010 1 次提交
  23. 28 8月, 2009 1 次提交
  24. 13 5月, 2009 1 次提交
  25. 24 2月, 2009 3 次提交