anchor.diff:  [[boot-features-caching-provider-ehcache2]]
   ==== EhCache 2.x
   EhCache 2.x is used if a file named `ehcache.xml` can be found at the root of the
  -classpath. If EhCache 2.x and such file is present it is used to bootstrap the cache
  -manager. An alternate configuration file can be provide a well using:
  +classpath. If EhCache 2.x, the `EhCacheCacheManager` provided by the
  +`spring-boot-starter-cache` '`Starter`' and such file is present it is used to bootstrap
  +the cache manager. An alternate configuration file can be provide a well using:
   
   [source,properties,indent=0]
   ----
  
positive.code: NOTE: If you are using the cache infrastructure with beans that are not interface-based,
  make sure to enable the `proxyTargetClass` attribute of `@EnableCaching`.
  
  TIP: Use the `spring-boot-starter-cache` '`Starter`' to quickly add required caching
  dependencies. If you are adding dependencies manually you should note that certain
  implementations are only provided by the `spring-context-support` jar.
  
  If you haven't defined a bean of type `CacheManager` or a `CacheResolver` named
  `cacheResolver` (see `CachingConfigurer`), Spring Boot tries to detect the following
  
negative.code: [[boot-features-caching-provider-jcache]]
  ==== JCache (JSR-107)
  JCache is bootstrapped via the presence of a `javax.cache.spi.CachingProvider` on the
  classpath (i.e. a JSR-107 compliant caching library) and the `JCacheCacheManager`
  provided by the `spring-boot-starter-cache` '`Starter`'. There are various compliant
  libraries out there and Spring Boot provides dependency management for Ehcache 3,
  Hazelcast and Infinispan. Any other compliant library can be added as well.
  
  It might happen that more than one provider is present, in which case the provider must
  be explicitly specified. Even if the JSR-107 standard does not enforce a standardized
  