What a build contains

What a build of an application with spring_boot_starter_cache contains, and when something is not in it. A module that follows a key reads it when build_runner runs, from application.yml or application.properties without a profile (see Modules left out of the build). The modules of the packages it depends on come with it: for spring_boot_dart, see Auto-configuration.

Always in

No build: and no platform:: in every build of an application that depends on the starter.

Module What it holds
springBootStarterCacheAutoConfiguration The default CacheManager built from spring.cache.* and the interceptor that runs @Cacheable, @CachePut and @CacheEvict.

By key

build: AutoConfigurationBuild(key): true puts the module in every build, false leaves it out with all its code, and when the key is not set the Not set column decides.

Module Key Not set What it holds
springBootStarterCacheStartupChecksAutoConfiguration spring.main.startup-checks.enabled debug and profile builds only cacheOperationValidator: checks the cache annotations of every proxied bean when it is created, so a wrong one stops the start. Without it a wrong annotation fails at the member's first call.

A module left to notInRelease is dropped from Flutter's release builds and from dart compile exe. dart run and dart compile js / wasm define no dart.vm.product, so there the module stays when the key is not set; only false leaves it out.

What the generator writes for it

A part of the generator (see Starter parts) runs only when the application reaches its package.

Part or builder What it does
Cache part (spring_boot_starter_cache) Writes nothing: says where the key, condition and unless expressions of the cache annotations look, so the classes they reach are described; @Cacheable or @CachePut on a method returning a Stream fails the build.

See also