anchor.diff:  cache capacity is not possible. To specify a meaningful cache configuration, the cache2k configuration mechanism
   needs to be utilized.
   
  -To create a JCache with an additional cache2k configuration the interface `ExtendedConfiguration` and the class `MutableExtendedConfiguration`
  -is provided.
  +==== Programmatic Configuration
  +
  +To create a JCache with an additional cache2k configuration the interface `ExtendedConfiguration`
  +and the class `MutableExtendedConfiguration` is provided. The configuration classes are available in
  +separate API packages, that need to be included in the compile scope:
  +
  +[source,xml,subs="attributes+"]
  +----
  +    <dependency>
  +      <groupId>org.cache2k</groupId>
  +      <artifactId>cache2k-api</artifactId>
  +      <version>${cache2k.version}</version>
  +      <scope>provided</scope>
  +    </dependency>
  +    <dependency>
  +      <groupId>org.cache2k</groupId>
  +      <artifactId>cache2k-jcache-api</artifactId>
  +      <version>${cache2k.version}</version>
  +    </dependency>
  +----
   
   Example usage:
   
  
positive.code: to the cache or retrieved from the cache.
  
  === Implementation Details
  
  ==== Expiry Policy
  
  
negative.code:     ));
  ----
  
  When a cache2k configuration is provided, the default behavior is not 100% JCache compatible any more, because
  the defaults of cache2k apply. Strict JCache behavior can be enabled again, if needed. The areas of difference
  are explained below:
  
  Expiry:: With pure JCache configuration the expiry is set to sharp expiry by default for maximum compatiblity. When the
     cache2k configuration is used, sharp expiry is off and need to be enabled explicitly.
  