- 25 2月, 2019 1 次提交
-
-
由 www 提交于
Closes gh-22463
-
- 21 11月, 2018 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-17518
-
- 28 6月, 2018 1 次提交
-
-
由 Phillip Webb 提交于
Fix checkstyle violations for javadoc. Issue: SPR-16968
-
- 23 6月, 2018 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16898
-
- 19 6月, 2018 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16898
-
- 16 2月, 2018 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 21 10月, 2017 1 次提交
-
- 17 8月, 2017 1 次提交
-
-
由 Sebastien Deleuze 提交于
Issue: SPR-15869
-
- 19 7月, 2017 1 次提交
-
-
由 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
-
- 07 6月, 2017 1 次提交
-
-
由 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
-
- 27 5月, 2017 1 次提交
-
-
由 Sebastien Deleuze 提交于
This commit introduces 2 new @Nullable and @NonNullApi annotations that leverage JSR 305 (dormant but available via Findbugs jsr305 dependency and already used by libraries like OkHttp) meta-annotations to specify explicitly null-safety of Spring Framework parameters and return values. In order to avoid adding too much annotations, the default is set at package level with @NonNullApi and @Nullable annotations are added when needed at parameter or return value level. These annotations are intended to be used on Spring Framework itself but also by other Spring projects. @Nullable annotations have been introduced based on Javadoc and search of patterns like "return null;". It is expected that nullability of Spring Framework API will be polished with complementary commits. In practice, this will make the whole Spring Framework API null-safe for Kotlin projects (when KT-10942 will be fixed) since Kotlin will be able to leverage these annotations to know if a parameter or a return value is nullable or not. But this is also useful for Java developers as well since IntelliJ IDEA, for example, also understands these annotations to generate warnings when unsafe nullable usages are detected. Issue: SPR-15540
-
- 31 1月, 2017 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-15196
-
- 05 7月, 2016 1 次提交
-
-
由 Stephane Nicoll 提交于
Issue: SPR-13188
-
- 30 6月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14321
-
- 28 6月, 2016 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14321
-
- 14 4月, 2015 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12818
-
- 21 10月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 29 12月, 2012 1 次提交
-
-
由 Chris Beams 提交于
Issue: SPR-10128
-
- 18 5月, 2012 1 次提交
-
-
由 Rossen Stoyanchev 提交于
See the commit comments for: https://github.com/SpringSource/spring-framework/commit/57307a0b2e5bce8f70d5deddf8df11d034dc8c5a This commit also applies the change to pre-3.1 `@mvc` suppor classes. Issue: SPR-6951
-
- 17 5月, 2012 1 次提交
-
-
由 Rossen Stoyanchev 提交于
SPR-9333
-
- 31 1月, 2012 1 次提交
-
-
由 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
-
- 20 5月, 2011 1 次提交
-
-
由 Rossen Stoyanchev 提交于
-
- 12 4月, 2011 1 次提交
-
-
由 Rossen Stoyanchev 提交于
-
- 06 4月, 2011 1 次提交
-
-
由 Rossen Stoyanchev 提交于
-
- 08 11月, 2010 1 次提交
-
-
由 Arjen Poutsma 提交于
-
- 13 8月, 2010 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 08 6月, 2010 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 13 3月, 2010 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 02 3月, 2010 1 次提交
-
-
由 Arjen Poutsma 提交于
-
- 18 2月, 2010 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 07 12月, 2009 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 30 11月, 2009 1 次提交
-
-
由 Keith Donald 提交于
added back mvc:interceptors element and added interceptor matching based on path pattern; needs review
-
- 25 11月, 2009 1 次提交
-
-
由 Arjen Poutsma 提交于
-
- 24 11月, 2009 1 次提交
-
-
由 Arjen Poutsma 提交于
-
- 25 9月, 2009 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 16 4月, 2009 1 次提交
-
-
由 Arjen Poutsma 提交于
-
- 20 1月, 2009 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 18 11月, 2008 1 次提交
-
-
由 Arjen Poutsma 提交于
-
- 28 10月, 2008 1 次提交
-
-
由 Arjen Poutsma 提交于
-
- 27 10月, 2008 1 次提交
-
-
由 Arjen Poutsma 提交于
-