- 18 12月, 2015 14 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13685
-
由 Juergen Hoeller 提交于
Issue: SPR-13230
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Sam Brannen 提交于
- Delete unused imports - Delete unused code - Clean up warnings
-
由 Juergen Hoeller 提交于
Issue: SPR-13235
-
由 Sam Brannen 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13229
-
由 Juergen Hoeller 提交于
Issue: SPR-13230
-
由 Juergen Hoeller 提交于
Issue: SPR-13235
-
由 Juergen Hoeller 提交于
Issue: SPR-13062
-
由 Juergen Hoeller 提交于
Issue: SPR-13729
-
由 Juergen Hoeller 提交于
Issue: SPR-13804
-
由 Sam Brannen 提交于
-
- 17 12月, 2015 7 次提交
-
-
由 Stephane Nicoll 提交于
-
由 Spring Buildmaster 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13802
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-13801
-
- 16 12月, 2015 2 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Brian Clozel 提交于
In several places in the spring-webmvc module, URL patterns / objects relationships are kept in `HashMap`s. When matching with actual URLs, the algorithm uses a pattern comparator to sort the matching patterns and select the most specific. But the underlying collection implementation does not keep the original order which can lead to inconsistencies. This commit changes the underlying collection implementation to `LinkedHashmap`s, in order to keep the insert order if the comparator does not reorder entries. Issue: SPR-13798
-
- 15 12月, 2015 8 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
- 14 12月, 2015 3 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13791
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
- 13 12月, 2015 2 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
- 12 12月, 2015 4 次提交
-
-
由 Andy Clement 提交于
Before this change the compilation of a method reference or property/field access was not properly cleaning up the stack if compilation meant calling a static method or accessing a static field. In these cases there is no need for a target object on the stack and it should be removed if present. For a simple expression it is harmless since the end result of the expression is the thing on the top of the stack, but for nested expressions if the inner expression suffered this issue, the outer expression can find itself operating on the wrong element. The particular issue covered the case of a static field access but this fix (and associated tests) cover static method, property and field access. Issue: SPR-13781
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Base64Utils: URL/File Safe Alphabet Issue: SPR-13784
-