- 27 8月, 2019 10 次提交
-
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
Prior to this commit, there was no way to replace the Set-Cookie header via MockHttpServletResponse. Specifically, an invocation of setHeader() for the Set-Cookie header resulted in an additional Set-Cookie header instead of replacing the existing one, which is in violation of the contract for javax.servlet.http.HttpServletResponse.setHeader(...). This commit refactors the internals of MockHttpServletResponse to ensure that an existing Set-Cookie header is overwritten when set via an invocation of setHeader(). This commit also verifies the expected behavior for addHeader() and addCookie() with regard to multiple cookies. Closes gh-23512
-
由 Sam Brannen 提交于
See gh-23514
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
This commit introduces a utility method for retrieving the original bean name for the target of a scoped proxy. Closes gh-23514
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
See gh-23458
-
由 Rossen Stoyanchev 提交于
For public use, these constants aren't ideally exposed through an SPI like MetadataExtractor, and there isn't any other obvious place either. In practice the only public API where these can be passed in is RSocketRequester and RSocketMessageHandler both of which already default to composite metadata anyway, leaving only the routing MimeType to be used potentially but much less likely. Due to existence of similar constants in the RSocket itself, i.e. WellKnownMimeType, we can get by internally too without declaring MimeType constants from a central place.
-
由 Rossen Stoyanchev 提交于
take advantage of the symmetrical SocketAcceptor methods now available on RSocketFactory for both client and server side.
-
由 lijuny 提交于
This commit polishes tests in spring-aop by using OrderComparator.sort() and lambda expressions instead of anonymous classes where feasible. Closes gh-23458
-
- 26 8月, 2019 3 次提交
-
-
由 Sam Brannen 提交于
-
由 Johnny Lim 提交于
Closes gh-23519
-
由 Sam Brannen 提交于
Prior to this commit, the AutowiredArgumentMarker type was repeatedly instantiated in ConstructorResolver. This commit replaces the AutowiredArgumentMarker type with a simple Object instance. Closes gh-23469
-
- 25 8月, 2019 2 次提交
-
-
由 Sam Brannen 提交于
See gh-23514
-
由 Sam Brannen 提交于
This commit introduces a utility method for retrieving the original bean name for the target of a scoped proxy. Closes gh-23514
-
- 23 8月, 2019 16 次提交
-
-
由 Brian Clozel 提交于
See gh-23506
-
由 Brian Clozel 提交于
See gh-23282
-
由 Sam Brannen 提交于
This is an attempt to solve a build issue on Microsoft Windows. See gh-23507
-
由 Sam Brannen 提交于
Closes gh-23504
-
由 Sam Brannen 提交于
Prior to this commit, the invokeMethod() utility method in ReflectionTestUtils only supported instance methods. This commit brings the invokeMethod() support on par with the getField() support by supporting the invocation of static methods via two new invokeMethod() variants. Closes gh-23504
-
由 Sam Brannen 提交于
-
由 Brian Clozel 提交于
See gh-23506
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
Due to a bug (or "unintentional feature") in JUnit 4, overridden test and lifecycle methods not annotated with @test, @Before, @after, etc. are still executed as test methods and lifecycle methods; however, JUnit Jupiter does not support that. Thus, prior to this commit, some overridden test and lifecycle methods were no longer executed after the migration from JUnit 4 to JUnit Jupiter. This commit addresses this issue for such known use cases, but there are likely other such use cases within Spring's test suite. See gh-23451
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Brian Clozel 提交于
This commit ensures that file streams are properly closed in tests. This seems to cause issues on Windows as the OS cannot delete temp folders. This is similar to spring-io/initializr#862 See gh-23507
-
由 Arjen Poutsma 提交于
Closes gh-23404
-
由 Lars Grefer 提交于
See gh-23282 See spring-projects/spring-security#7183 Closes gh-23506
-
- 22 8月, 2019 5 次提交
-
-
由 Sebastien Deleuze 提交于
See gh-21778
-
由 Brian Clozel 提交于
This commit ensures that Gradle publications are using resolved dependency versions for Maven publications (i.e. POMs). This is useful since we're using the Spring dependency management plugin and we can't rely on declared dependency versions only. See gh-23282
-
由 Rossen Stoyanchev 提交于
See gh-22644
-
由 Brian Clozel 提交于
Instead of relying on the CI server to apply and configure this plugin, this commit does it directly in the Spring Framework build. This allows us to take full control over which projects are published and how. See gh-23282
-
由 Brian Clozel 提交于
This commit switches to the default publication name considered by the artifactory plugin when it comes to publishing artifacts to the artifactory repository. See gh-23282
-
- 21 8月, 2019 4 次提交
-
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Brian Clozel 提交于
Prior to this commit, the build would use a custom task to create a BOM and manually include/exclude/customize dependencies. It would also use the "maven" plugin to customize the POM before publication. This commit now uses a Gradle Java Platform for publishing the Spring Framework BOM. We're also now using the "maven-publish" plugin to prepare and customize publications. This commit also tells the artifactory plugin (which is currently applied only on the CI) not to publish internal modules. See gh-23282
-
由 Brian Clozel 提交于
This commit configures the Gradle Download plugin that's used a build step when generating the reference documentation. Here we're making sure that the task is caching and reusing the resource if it's been downloaded already. See gh-23282
-