- 12 3月, 2019 1 次提交
-
-
由 Jorg Heymans 提交于
See gh-22572
-
- 22 11月, 2018 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-15540
-
- 08 8月, 2018 1 次提交
-
-
由 Kazuhiro Sera 提交于
-
- 19 7月, 2018 1 次提交
-
-
由 Juergen Hoeller 提交于
LinkedList remains in place where a List is likely to remain empty or single-element (in order to avoid unused capacity). Issue: SPR-17037
-
- 28 6月, 2018 4 次提交
-
-
由 Phillip Webb 提交于
Reorganize imports to ensure consistent ordering. This commit also expands any `.*` static imports in favor of using fully-qualified method references. Issue: SPR-16968
-
由 Phillip Webb 提交于
Update code that has accidentally used spaces instead of tabs. Also remove all trailing whitespace. Issue: SPR-16968
-
由 Phillip Webb 提交于
Ensure that `this.` is used consistently when accessing class fields. Issue: SPR-16968
-
由 Phillip Webb 提交于
Fix checkstyle violations for javadoc. Issue: SPR-16968
-
- 10 5月, 2018 1 次提交
-
-
由 nkjackzhang 提交于
Closes gh-1824
-
- 09 3月, 2018 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 10 2月, 2018 1 次提交
-
-
由 igor-suhorukov 提交于
-
- 27 9月, 2017 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-15656
-
- 15 9月, 2017 1 次提交
-
-
由 Sebastien Deleuze 提交于
This commit introduces the following changes. 1) It adds a new Spring @NonNull annotation which allows to apply @NonNullApi semantic on a specific element, like @Nullable does. Combined with @Nullable, it allows partial null-safety support when package granularity is too broad. 2) @Nullable and @NonNull can apply to ElementType.TYPE_USE in order to be used on generic type arguments (SPR-15942). 3) Annotations does not apply to ElementType.TYPE_PARAMETER anymore since it is not supported yet (applicability for such use case is controversial and need to be discussed). 4) @NonNullApi does not apply to ElementType.FIELD anymore since in a lot of use cases (private, protected) it is not part for the public API + its usage should remain opt-in. A dedicated @NonNullFields annotation has been added in order to set fields default to non-nullable. 5) Updated Javadoc and reference documentation. Issue: SPR-15756
-
- 17 8月, 2017 1 次提交
-
-
由 Sebastien Deleuze 提交于
Issue: SPR-15869
-
- 30 6月, 2017 1 次提交
-
-
由 Juergen Hoeller 提交于
This commits extends nullability declarations to the field level, formalizing the interaction between methods and their underlying fields and therefore avoiding any nullability mismatch. Issue: SPR-15720
-
- 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
-
- 01 6月, 2017 1 次提交
-
-
由 Sebastien Deleuze 提交于
Issue: SPR-15540
-
- 31 5月, 2017 1 次提交
-
-
由 Sebastien Deleuze 提交于
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
-
- 16 2月, 2017 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14670
-
- 20 7月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14489
-
- 05 7月, 2016 1 次提交
-
-
由 Stephane Nicoll 提交于
Issue: SPR-13188
-
- 12 4月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 28 10月, 2015 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13617
-
- 21 10月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 08 8月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 10 4月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-11600
-
- 26 11月, 2013 1 次提交
-
-
由 Phillip Webb 提交于
Fix remaining Java compiler warnings, mainly around missing generics or deprecated code. Also add the `-Werror` compiler option to ensure that any future warnings will fail the build. Issue: SPR-11064
-
- 14 5月, 2013 1 次提交
-
-
由 Rob Winch 提交于
Issue: SPR-10130
-
- 02 1月, 2013 1 次提交
-
-
由 Chris Beams 提交于
This reverts commit 45fa5082, reversing changes made to a312d900.
-
- 29 12月, 2012 4 次提交
-
-
由 Chris Beams 提交于
Issue: SPR-10130
-
由 Chris Beams 提交于
-
由 Chris Beams 提交于
Issue: SPR-10128
-
由 Phillip Webb 提交于
find . -type f -name "*.java" -or -name "*.aj" | \ xargs perl -p -i -e "s/[ \t]*$//g" {} \; Issue: SPR-10127
-
- 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
-