From a20d2ccb176ef89adea7e873027ed62dd97b697b Mon Sep 17 00:00:00 2001 From: Mark Paluch Date: Mon, 8 Sep 2025 11:46:46 +0200 Subject: [PATCH] Refine version properties for documentation build. See spring-projects/spring-data-build#2638 --- src/main/antora/modules/ROOT/pages/r2dbc/getting-started.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/antora/modules/ROOT/pages/r2dbc/getting-started.adoc b/src/main/antora/modules/ROOT/pages/r2dbc/getting-started.adoc index d60e42a01..c5e5ffec9 100644 --- a/src/main/antora/modules/ROOT/pages/r2dbc/getting-started.adoc +++ b/src/main/antora/modules/ROOT/pages/r2dbc/getting-started.adoc @@ -178,7 +178,7 @@ Alternatively, you can implement your own `Dialect`. [TIP] ==== -Dialects are resolved by {spring-data-r2dbc-javadoc}/org/springframework/data/r2dbc/dialect/DialectResolver.html[`DialectResolver`] from a `ConnectionFactory`, typically by inspecting `ConnectionFactoryMetadata`. +Dialects are resolved by javadoc:org.springframework.data.r2dbc./dialect.DialectResolver[] from a `ConnectionFactory`, typically by inspecting `ConnectionFactoryMetadata`. + You can let Spring auto-discover your `R2dbcDialect` by registering a class that implements `org.springframework.data.r2dbc.dialect.DialectResolver$R2dbcDialectProvider` through `META-INF/spring.factories`. `DialectResolver` discovers dialect provider implementations from the class path using Spring's `SpringFactoriesLoader`. To do so: