Fix broken link to Spring Framework reference documentation.

Closes gh-955

Author: mp911de

src/main/antora/modules/ROOT/pages/vault/authentication.adoc

@@ -15,7 +15,7 @@ Disclosure of login credentials to any party allows login to Vault and access se
 are permitted by the underlying role. Picking the appropriate client authentication and
 injecting credentials into the application is subject to risk evaluation.
 
-Spring's {spring-framework-docs}core.html#beans-property-source-abstraction[PropertySource abstraction] is a natural fit
+Spring's {spring-framework-docs}/core/beans/environment.html#beans-property-source-abstraction[PropertySource abstraction] is a natural fit
 to keep configuration outside the application code. You can use system properties, environment
 variables or property files to store login credentials. Each approach comes with its own properties.
 Keep in mind that the command line and environment properties can be introspected with appropriate

src/main/antora/modules/ROOT/pages/vault/client-support.adoc

@@ -2,7 +2,7 @@
 = Client support
 
 Spring Vault supports various HTTP clients to access Vault's HTTP API. Spring Vault uses
-{spring-framework-docs}integration.html#rest-resttemplate[`RestTemplate`] as primary interface accessing Vault.
+{spring-framework-docs}/integration/rest-clients.html#rest-resttemplate[`RestTemplate`] as primary interface accessing Vault.
 Dedicated client support originates from <<vault.client-ssl,customized SSL configuration>>
 that is scoped only to Spring Vault's client components.
 

src/main/antora/modules/ROOT/pages/vault/imperative-template.adoc

@@ -45,7 +45,7 @@ Now let's look at a examples of how to work with Vault in the context of the Spr
 
 Using Spring Vault does not require a Spring Context. However, instances of `VaultTemplate` and
 javadoc:org.springframework.vault.authentication.SessionManager[] registered inside a managed context will participate
-in {spring-framework-docs}core.html#beans-factory-nature[lifecycle events]
+in {spring-framework-docs}/core/beans/factory-nature.html[lifecycle events]
 provided by the Spring IoC container. This is useful to dispose active Vault sessions upon
 application shutdown. You also benefit from reusing the same `VaultTemplate`
 instance across your application.

src/main/antora/modules/ROOT/pages/vault/propertysource.adoc

@@ -3,7 +3,7 @@
 
 Vault can be used in many different ways. One specific use-case is using
 Vault to store encrypted properties. Spring Vault supports Vault as property
-source to obtain configuration properties using Spring's {spring-framework-docs}core.html#beans-property-source-abstraction[PropertySource abstraction].
+source to obtain configuration properties using Spring's {spring-framework-docs}/core/beans/environment.html#beans-property-source-abstraction[PropertySource abstraction].
 
 NOTE: You can reference properties stored inside Vault in other property sources or use value injection with `@Value(…)`. Special attention is required when bootstrapping beans that require data stored inside of Vault. A javadoc:org.springframework.vault.core.env.VaultPropertySource[] must be initialized at that time to retrieve properties from Vault.
 
@@ -101,7 +101,7 @@ NOTE: Secrets obtained from `generic` secret backends are associated with a TTL
 
 NOTE: You can use `@VaultPropertySource` to obtain the newest secret version from the versioned Key-Value backend. Make sure to not include the `data/` segment in the path.
 
-Any `${…​}` placeholders present in a `@VaultPropertySource` path are resolved against the set of property sources already registered against the environment, as the following example shows:
+Any `${…}` placeholders present in a `@VaultPropertySource` path are resolved against the set of property sources already registered against the environment, as the following example shows:
 
 .Declaring a `@VaultPropertySource` path using placeholders
 ====

src/main/antora/modules/ROOT/pages/vault/reactive-template.adoc

@@ -67,7 +67,7 @@ Now let's look at examples of how to work with Vault in the context of the Sprin
 
 Using Spring Vault does not require a Spring Context. However, instances of
 javadoc:org.springframework.vault.core.ReactiveVaultTemplate[] and `VaultTokenSupplier` registered inside a managed context will participate
-in {spring-framework-docs}core.html#beans-factory-nature[lifecycle events]
+in {spring-framework-docs}/core/beans/factory-nature.html[lifecycle events]
 provided by the Spring IoC container. This is useful to dispose active Vault sessions upon
 application shutdown. You also benefit from reusing the same javadoc:org.springframework.vault.core.ReactiveVaultTemplate[]
 instance across your application.

src/main/antora/resources/antora-resources/antora.yml

@@ -8,10 +8,5 @@ asciidoc:
     springversionshort: ${spring.version.short}
     springversion: ${spring.version}
     attribute-missing: 'warn'
-    include-xml-namespaces: false
-    spring-data-commons-docs-url: https://docs.spring.io/spring-data/commons/reference
-    spring-data-commons-javadoc-base: https://docs.spring.io/spring-data/commons/docs/current/api/
     spring-framework-docs: https://docs.spring.io/spring-framework/reference/{springversionshort}
-    springjavadocurl: https://docs.spring.io/spring-framework/docs/${spring.version}/javadoc-api
-    spring-framework-javadoc: '{springjavadocurl}'
     springDataVersion: ${spring-data-bom.version}