1. 20 Apr, 2017 3 commits
    • Dave Syer's avatar
      Extended PropertiesLauncher class location logic · 14638e67
      Dave Syer authored
      Update `PropertiesLauncher` so that classes can be loaded outside of
      `BOOT-INF/classes`. You can use a subdirectory, or the root directory
      of an external jar (but not the parent archive to avoid issues
      with agents and awkward delegation models).
      
      Fixes gh-8480
      Closes gh-8486
      14638e67
    • Phillip Webb's avatar
      Support detection and with test initializers · 5abc050a
      Phillip Webb authored
      Relax `SpringBootTestContextBootstrapper` rules so that a test can
      specify an `ApplicationContextInitializer` and still have
      `@SpringBootConfiguration` detected.
      
      Prior to this commit detection would not occur because it's possible
      that an initializer _could_ register configuration. This scenario is
      actually quite unlikely to occur, certainly less likely than wanting to
      use an initializer in combination with auto-detection.
      
      Fixes gh-8483
      5abc050a
    • Phillip Webb's avatar
      Refine validator and MVC validator configuration · c9561f03
      Phillip Webb authored
      Update `ValidationAutoConfiguration` and `WebMvcAutoConfiguration` to
      ensure as much as possible that only a single Validator bean of each
      type is registered.
      
      Validation auto-configuration now does the following:
      - If no validator is found: Registers a `LocalValidatorFactoryBean`
        (providing both Spring and JSR validation)
      - If the user defines a Spring & JSR validator: Backs off
      - If the user defines only a JSR validator: Adapts it to a Spring
        validator (without exposing another JSR implementation)
      
      WebMvcAutoConfiguration auto-configuration has been updated to make
      MVC validation follow common Spring Boot patterns:
      - If not validator beans are found (due to the user excluding
        ValidationAutoConfiguration) a new `mvcValidator` bean will be
        registered.
      - If a single validator bean is found it will be used for MVC
        validation.
      - If multiple validator beans are defined it will either use the one
        named `mvcValidator` or it will register a new `mvcValidator` bean
      
      Any automatically registered `mvcValidator` bean will not implement
      the JSR validator interface.
      
      Finally, it is no longer possible to provide an MVC validator via a
      `WebMvcConfigurer`.
      
      Fixes gh-8495
      c9561f03
  2. 19 Apr, 2017 19 commits
  3. 18 Apr, 2017 13 commits
  4. 17 Apr, 2017 2 commits
  5. 14 Apr, 2017 3 commits