anchor.diff:  to the method outcome.
   
   Note that `void` methods can be used with `@CacheEvict` - as the
  -methods act as a trigger, the return values are ignored (as they do nt interact with the
  +methods act as a trigger, the return values are ignored (as they do not interact with the
   cache). This is not the case with `@Cacheable` which adds or updates data into the cache
   and, thus, requires a result.
   
  
positive.code: that are affected by the action, allows a custom cache and key resolution or a
  condition to be specified, and features an extra parameter
  (`allEntries`) that indicates whether a cache-wide eviction needs to be performed
  rather then just an entry eviction (based on the key). The following example evicts
  all entries from the `books` cache:
  
  [source,java,indent=0]
  
negative.code: 
  
  This option comes in handy when an entire cache region needs to be cleared out. Rather
  than evicting each entry (which would take a long time, since it is inefficient), all the
  entries are removed in one operation, as the preceding example shows. Note that the framework ignores
  any key specified in this scenario as it does not apply (the entire cache is evicted, not
  only one entry).
  