With this commit, the Maven `spring-boot:build-image` goal and the
Gradle `bootBuildImage` task will configure the OpenJDK buildpack
to use the same JRE version as the project's target version,
provided the buildpack Java version is not explicitly set in the
build configuration.

Fixes gh-20172

Closes gh-20240

Cloes gh-20199

Closes gh-20197

* gh-20179:
  Polish "Allow Gradle tasks to be executed with a custom Java home"
  Allow Gradle tasks to be executed with a custom Java home

Closes gh-20179

See gh-20179

See gh-20179

Closes gh-19988
Co-authored-by: Mark Paluch <mpaluch@pivotal.io>

See gh-19988
Co-authored-by: Mark Paluch <mpaluch@pivotal.io>

This commit adds metrics support for `ConnectionPool` beans.

See gh-19988
Co-authored-by: Mark Paluch <mpaluch@pivotal.io>
Co-authored-by: Tadaya Tsuyukubo <tadaya@ttddyy.net>

This commit adds an health indicator for R2DBC. If a validation query is
provided, it is used to validate the state of the database. If not, a
check of the connection is issued.

See gh-19988
Co-authored-by: Mark Paluch <mpaluch@pivotal.io>

This commit adds a test slice for Spring Data R2DBC. When
`DataR2dbcTest` is added on a test, only Spring Data R2DBC repositories
and the infrastructure that they need is auto-configured.

Contrary to the JDBC counterpart, the `ConnectionFactory` is not swapped
by an embedded database.

See gh-19988
Co-authored-by: Mark Paluch <mpaluch@pivotal.io>

This commit adds auto-configuration support for Spring Data R2DBC. If a
`ConnectionFactory` and Spring Data are available, scanning of reactive
repositories is enabled.

This commit also adds a starter to bring R2DBC and the necessary Spring
Data libraries.

See gh-19988
Co-authored-by: Mark Paluch <mpaluch@pivotal.io>
Co-authored-by: Oliver Drotbohm <odrotbohm@pivotal.io>

This commit adds auto-configuration for R2DBC. If R2DBC is on the
classpath, a `ConnectionFactory` is created similarly to the algorithm
used to create a `DataSource`.

If an url is specified, it is used to determine the R2DBC driver and
database location. If not, an embedded database is started (with only
support of H2 via r2dbc-h2). If none of those succeed, an exception is
thrown that is handled by a dedicated FailureAnalyzer.

To clearly separate reactive from imperative access, a `DataSource` is
not auto-configured if a `ConnectionFactory` is present. This makes sure
that any auto-configuration that relies on the presence of a
`DataSource` backs off.

There is no dedicated database initialization at the moment but it is
possible to configure flyway or liquibase to create a local `DataSource`
for the duration of the migration. Alternatively, if Spring Data R2DBC
is on the classpath, a `ResourceDatabasePopulator` bean can be defined
with the scripts to execute on startup.

See gh-19988
Co-authored-by: Mark Paluch <mpaluch@pivotal.io>

Closes gh-20315

* pr/20313:
  Fix typos in documentation

Closes gh-20313

See gh-20313

* pr/20309:
  Upgrade to Gradle 6.2.1

Closes gh-20309

See gh-20309

* pr/20310:
  Test the Gradle plugin against Gradle 6.2.1

Closes gh-20310

See gh-20310

Closes gh-20312

Closes gh-20200

Closes gh-20196

Closes gh-20307

Closes gh-20306

Fixes gh-20134

* pr/20242:
  Explicitly set java home in CommandLineInvoker

Closes gh-20242

See gh-20242

Closes gh-20293

Closes gh-20292

See gh-12951
See gh-20291