- 23 Mar, 2021 3 commits
-
-
Andy Wilkinson authored
Closes gh-25762
-
Andy Wilkinson authored
Closes gh-25761
-
Andy Wilkinson authored
Closes gh-25760
-
- 22 Mar, 2021 8 commits
-
-
Andy Wilkinson authored
Closes gh-25487 Closes gh-25756
-
Andy Wilkinson authored
Closes gh-25757
-
Stephane Nicoll authored
Closes gh-25755
-
Stephane Nicoll authored
Closes gh-25754
-
Stephane Nicoll authored
* pr/25129: Polish "Take JPA database action into account when setting ddlAuto" Take JPA database action into account when setting ddlAuto Closes gh-25129
-
Stephane Nicoll authored
See gh-25129
-
bono007 authored
See gh-25129
-
Andy Wilkinson authored
Closes gh-21045
-
- 19 Mar, 2021 9 commits
-
-
Scott Frederick authored
Closes gh-25701
-
Scott Frederick authored
Closes gh-25700
-
Andy Wilkinson authored
Closes gh-24225
-
Andy Wilkinson authored
Closes gh-25747
-
Phillip Webb authored
Closes gh-25553
-
Phillip Webb authored
Closes gh-25564
-
Andy Wilkinson authored
Update `PrometheusScrapeEndpoint` so that it can produce both classic Prometheus text output as well as Openmetrics output. See gh-25564
-
Phillip Webb authored
Refine the new `Producible` support so that it can also be used with `@ReadOperation`, `@WriteOperation` and `@DeleteOperation` annotations. This update allows the same enum to be used both as an argument and as an indicator of the media-types that an operation may produce. Closes gh-25738
-
Andy Wilkinson authored
Update the actuator @Enpoint` infrastructure code so that operations may inject enums that indicate the type of output to produce. A new `Producible` interface can be implemented by any enum that indicates the mime-type that an enum value produces. The new `OperationArgumentResolver` provides a general strategy for resolving operation arguments with `ProducibleOperationArgumentResolver` providing support for `Producible` enums. Existing injection support has been refactored to use the new resolver. See gh-25738
-
- 18 Mar, 2021 16 commits
-
-
Phillip Webb authored
-
Phillip Webb authored
-
Phillip Webb authored
Polish the prefix support introduced in commit a8592f36 and fix a package tangle between `boot.context.properties.source` and `boot.env`. The `Prefix` interface has now been moved into a new default method on `OriginLookup`. See gh-3450
-
Stephane Nicoll authored
-
Spring Buildmaster authored
-
Stephane Nicoll authored
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Closes gh-25580
-
Stephane Nicoll authored
Closes gh-25579
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Closes gh-25582
-
Stephane Nicoll authored
Closes gh-25648
-
Stephane Nicoll authored
Closes gh-25577
-
Stephane Nicoll authored
Closes gh-25646
-
Phillip Webb authored
Update `FlywayAutoConfiguration`, `LiquibaseAutoConfiguration` and `DataSourceInitializer` classes so that they no longer depend on `DataSourceProperties`. DB migrations can now be performed against a `@Bean` defined primary `DataSource` with an alternative username/password. This update also removed using fallback properties when a custom connection `url` is defined with Flyway or Liquibase. We now assume that `username`, `password` and `driver-class-name` will be provided if the default values are unacceptable. Our previous logic was particularly flawed if a custom URL caused a change of driver type. Closes gh-25643
-
Phillip Webb authored
Refactor `DataSourceBuilder` to use direct property mappers rather than the `Binder` and aliases. Supported DataSource types now include two-way mappers which allows us to both get and set properties in a uniform way. A new `derivedFrom` factory method has been added which allows a new `DataSource` to be derived from an existing one. This update is primarily to allow Flyway and Liquibase migrations to work against a `@Bean` configured DataSource rather than assuming that the primary DataSource was always created via auto-configuration. See gh-25643
-
- 17 Mar, 2021 4 commits
-
-
Phillip Webb authored
Align our property with the recently changed spring-kafka default. Closes gh-25730
-
Scott Frederick authored
When the `finalName` parameter is incorrectly set in the Spring Boot Maven plugin configuration instead of in the `build` configuration, the repackaged and original archive files are not named as expected. Prior to this commit, the image building goal would detect this error condition and throw an exception late in the process of creating the build container, leaving the container in an unstable state. This commit changes the image building goal to detect this condition early, before attempting to create the container. Fixes gh-25590
-
Andy Wilkinson authored
-
Andy Wilkinson authored
Closes gh-25647
-