From fd76c7d0a352a917f05634c6ee71d673a323c731 Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Wed, 19 Apr 2023 13:30:39 +0200 Subject: [PATCH] Document default metadata cache expiration policy Closes gh-1391 --- .../src/main/asciidoc/configuration-guide.adoc | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/initializr-docs/src/main/asciidoc/configuration-guide.adoc b/initializr-docs/src/main/asciidoc/configuration-guide.adoc index 3bed9867..00ad5d5b 100644 --- a/initializr-docs/src/main/asciidoc/configuration-guide.adoc +++ b/initializr-docs/src/main/asciidoc/configuration-guide.adoc @@ -1155,8 +1155,12 @@ automatically: If you use the service, you'll notice that the logs have lots of entries with the message `Fetching boot metadata from https://api.spring.io/projects/spring-boot/releases`. To avoid checking for the latest Spring Boot versions too often, you should enable caching on your -service. Spring Initializr has some auto-configuration to apply the proper caches if you -are willing to use a JCache (JSR-107) implementation. +service. + +Spring Initializr has an auto-configuration for the requested caches if you are willing to +use a JCache (JSR-107) implementation. By default, the service metadata cache is +configured with an expiration policy that allows entries to remain in the cache for 10 +minutes. NOTE: The caches are created with an auto-configured `JCacheManagerCustomizer` with order `0` and only if they don't exist already. You can contribute a bean of the same type with a lower `@Order` to override some of the configuration to suit your specific needs.