Skip to content

S
spring-framework

爱吃血肠 / spring-framework

通知 1
Star 0
Fork 0
S
spring-framework

前往新版Gitcode，体验更适合开发者的 AI 搜索 >>

切换分支/标签
  1. 22 3月, 2019 1 次提交
  3. 15 3月, 2019 1 次提交
  5. 06 3月, 2019 1 次提交
  7. 04 3月, 2019 1 次提交
  9. 03 3月, 2019 2 次提交
  11. 02 3月, 2019 1 次提交
  13. 01 3月, 2019 2 次提交
  15. 24 11月, 2018 1 次提交
  17. 23 11月, 2018 1 次提交
    • S
      Ensure that parameter resolution in SpringExtension is thread-safe · aa7f69a5
      由 Sam Brannen 提交于 
      Prior to this commit, parallel execution of @BeforeEach and @AfterEach
methods that accepted @Autowired arguments would fail intermittently
due to a race condition in the internal implementation of the JDK's
java.lang.reflect.Executable.getParameters() method.

This commit addresses this issue by creating instances of
SynthesizingMethodParameter via
SynthesizingMethodParameter.forExecutable(Executable, int) instead of
SynthesizingMethodParameter.forParameter(Parameter), since the latter
looks up the parameter index by iterating over the array returned by
Executable.getParameters() (which is not thread-safe).

Issue: SPR-17533
      aa7f69a5
  19. 19 11月, 2018 2 次提交
  21. 10 11月, 2018 3 次提交
  23. 24 8月, 2018 1 次提交
  25. 15 8月, 2018 1 次提交
    • S
      Allow directly present @BootstrapWith to override meta annotations · d20d95b7
      由 Sam Brannen 提交于 
      Prior to this commit, if a test class was meta-annotated with multiple
@BootstrapWith declarations that registered different
TestContextBootstrapper implementations, such a configuration would
result in an IllegalStateException, and there was no way to override
this behavior.

This commit addresses this shortcoming by relaxing the explicit
TestContextBootstrapper resolution in BootstrapUtils so that a directly
present @BootstrapWith annotation will now override declarations of
@BootstrapWith that are meta-present. In other words, if @BootstrapWith
is used as a meta-annotation, it can be overridden directly on the test
class via an explicit, local declaration of @BootstrapWith.

Issue: SPR-17006
      d20d95b7
  27. 04 7月, 2018 3 次提交
  29. 28 6月, 2018 1 次提交
  31. 09 5月, 2018 1 次提交
  33. 23 4月, 2018 1 次提交
  35. 14 4月, 2018 1 次提交
  37. 12 4月, 2018 3 次提交
  39. 04 4月, 2018 2 次提交
    • S
      Use Gradle 4.6's built-in support for the JUnit Platform · 56774baa
      由 Sam Brannen 提交于 
      Gradle 4.6 provides built-in support for the JUnit Platform within the
standard `test` task.

This commit configures a custom `testJUnitJupiter` test task for
executing JUnit Jupiter tests directly on the JUnit Platform instead of
indirectly on JUnit 4 via @RunWith(JUnitPlatform.class).

This switch provides for better integration with Gradle's test reporting
and paves the way for a possible transition to the JUnit Platform in the
future.

Issue: SPR-16672
      56774baa
    • S
      Upgrade to JUnit Jupiter 5.1 · 71cacff8
      由 Sam Brannen 提交于 
      Issue: SPR-16408
      71cacff8
  41. 30 3月, 2018 1 次提交
  43. 29 3月, 2018 1 次提交
    • S
      Support DI of individual constructor args in @Nested tests · 9244090b
      由 Sam Brannen 提交于 
      Prior to this commit it was impossible to have an individual
constructor argument in a @Nested (i.e., inner) test class injected via
@Autowired, @Qualifier, or @Value.

This is due to a bug in javac on JDK versions prior to 9, whereby
annotation lookups performed directly via the
java.lang.reflect.Parameter API fail for inner class constructors.

Specifically, the parameter annotations array in the compiled byte code
for the user's test class excludes an entry for the implicit enclosing
instance parameter for an inner class constructor.

This commit introduces a workaround in ParameterAutowireUtils for this
off-by-one error by transparently looking up annotations on the
preceding Parameter object (i.e., index - 1). In addition, this commit
relies on the change recently introduced in MethodParameter in order to
compensate for the same JDK bug (see SPR-16652).

Issue: SPR-16653
      9244090b
  45. 27 3月, 2018 1 次提交
  47. 05 3月, 2018 1 次提交
  49. 14 2月, 2018 1 次提交
  51. 13 1月, 2018 1 次提交
  53. 06 9月, 2017 2 次提交
  55. 23 8月, 2017 1 次提交
  57. 07 7月, 2017 1 次提交