This change log lists the changes since 2.6.0.Final.

Fixes and Improvements

• Timer: Reduce scheduler events
• Timer: Correct scheduling time if an earlier expiry is inserted. Maximum lag time criteria was not met in this case.
• Timer: Rare case if only one cache entry with TTL and regular updates is used, leeds to continuous increase of scheduling events

Using this cache2k version

The binaries are available on maven central.

For Java SE/EE and Android environments

For Maven users:

    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>cache2k-api</artifactId>
      <version>2.6.1.Final</version>
    </dependency>
    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>cache2k-core</artifactId>
      <version>2.6.1.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

def cache2kVersion = '2.6.1.Final'

dependencies {
    implementation "org.cache2k:cache2k-api:${cache2kVersion}"
    runtimeOnly "org.cache2k:cache2k-core:${cache2kVersion}"
}

Using the JCache / JSR107 provider

Maven users include the cache2k JCache provider this way:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-jcache</artifactId>
      <version>2.6.1.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

dependencies {
    runtimeOnly "org.cache2k:cache2k-jcache:2.6.1.Final"
}

Implementation details, tuning tips and hints on configuration can be found at: JCache - cache2k User Guide

This change log lists the changes since 2.4.1.Final.

New and Noteworthy

• Idle scan: an efficient expire after access / time to idle alternative, Github issue #39
• Lots of cleanup and housekeeping with some minor changes possibly breaking compatibility
• Test coverage improvement and removal of unused code
• Cache disable support, Github issue #74
• Continuous Android testing

Updated benchmarks comparing with Caffeine 3.0.5, and EHCache3 3.9.6

Possible breakages

Changes that may break existing applications.

• Spring support: SpringCache2kManager.defaultSetup throws IllegalStateException if not called before caches are added
• Spring support: SpringCache2kManager.defaultSetup throws IllegalStateException if called twice
• EXPIRY_NOT_ETERNAL constant removed from Cache2kConfig
• Fixed generic typing issues in org.cache2k.config package
• Sechduler.schedule uses delay duration instead of absolute time
• TimeReference.millis() renamed to ticks() and additional conversion methods to support other time resolutions than milliseconds
• Safety gap system property for sharp timeout changed to: org.cache2k.sharpExpirySafetyGapMillis
• Removed capability to modify internal constants via Tunable
• removed SpringCache2kCacheManager.setCaches(Collection<Cache2kConfig<?, ?>> cacheConfigurationList)
• Corrected signature BulkCacheLoader.BulkCallback.onLoadFailure(Set, Exception) to onLoadFailure(Iterable, Exception)
• Cache.expireAt() and MutableCacheEntry.setExpiryTime(): the maximum expiry time is capped by the specified expireAfterWriteDuration, this aligns the behavior with the ExpiryPolicy. The rationale is, that an (application) user, when setting expireAfterWrite expects that this duration is never exceeded.

API Changes

• Added CacheClosedException
• Added CacheEventListenerException

Fixes and Improvements

• Eviction improvements, minimal change to improve eviction, See issue comment
• eternal(true/false) / MutableEntry.setExpiryTime: Expiry can be modified, although no other expiry setting is present, or in other words: the timer support is available by default. If eternal(true) is configured, timer support is disabled and Cache.invoke / MutableEntry.setExpiryTime or Cache.expireAt cannot be used
• Cache.invoke / MutableEntry.setExpiryTime: has no effect if entry is not existing
• Cache.invoke / MutableEntry.getExpiryTime always returns positive time value
• CI tests with Android API level 26 and API level 30
• Expiry timer: handle time values close up to Long.MAX_VALUE - 1 without overflow
• Support Duration for duration parameters in the Cache2kBuilder
• Config section InternalConfig in cache2k-core for specific tuning values that should not be exposed in the public API
• Spring support: SpringCache2kManager.setDefaultCacheNames() added
• Spring support: SpringCache2kManager.addCache(String, Function)
• Spring support: SpringCache2kCacheManager.getCache aligned with interface contract: returns null if unknown cache name is requested
• CacheClosedListener: Wait for CompletableFuture
• Simplify integrity checking, remove integrity state from toString output
• API: add/correct @Nullable annotations in ExpiryPolicy and AsyncCacheLoader
• Cache.invoke: Set expiry time correctly for exception propagation, in case setException and setExpiry is used atomically
• CacheInfo.getExpiryAfterWriteTicks, CacheInfo.getTimeReference(): added
• CacheControl.getCapacityLimit returns maximum weight correctly when weigher is present
• JCache: simplify implementation with access expiry and Cache.getAll
• JCache: Corrected access expiry handling for Cache.invoke / Cache.invokeAll

Non Functional Improvements

• Some tests migrated to JUnit 5 and AspectJ
• Various documentation touch ups
• Documentation and examples for expiry and expiry policy
• Examples for expiry policy in ExpiryPolicyExampleTest unit test
• Documentation improvements, fixed many typos and grammar errors in the API package

Credits

• Marcel Schnelle, mannodermaus for the contribution of Android CI tests, PR#178

Using this cache2k version

The binaries are available on maven central.

For Java SE/EE and Android environments

For Maven users:

    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>cache2k-api</artifactId>
      <version>2.6.0.Final</version>
    </dependency>
    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>cache2k-core</artifactId>
      <version>2.6.0.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

def cache2kVersion = '2.6.0.Final'

dependencies {
    implementation "org.cache2k:cache2k-api:${cache2kVersion}"
    runtimeOnly "org.cache2k:cache2k-core:${cache2kVersion}"
}

Using the JCache / JSR107 provider

Maven users include the cache2k JCache provider this way:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-jcache</artifactId>
      <version>2.6.0.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

dependencies {
    runtimeOnly "org.cache2k:cache2k-jcache:2.6.0.Final"
}

Implementation details, tuning tips and hints on configuration can be found at: JCache - cache2k User Guide

This is a preview release for evaluation purposes and should not be used in production. The final release is planed as "Cogee Beach" - 2.6.0.Final.

API Change

• Added CacheClosedException, moved from org.cache2k.core

Fixes and Improvements

• CacheClosedListener: Wait for CompletableFuture
• Simplify integrity checking, remove integrity state from toString output
• API: add/correct @Nullable annotations in ExpiryPolicy and AsyncCacheLoader
• Cache.invoke: Set expiry time correctly for exception propagation, in case setException and setExpiry is used atomically
• CacheInfo.getExpiryAfterWriteTicks, CacheInfo.getTimeReference(): added

Possible breakages

• Cache.expireAt() and MutableCacheEntry.setExpiryTime(): the maximum expiry time is capped by the specified expireAfterWriteDuration, this aligns the behavior with the ExpiryPolicy. The rationale is, that an (application) user, when setting expireAfterWrite expects that this duration is never exceeded.
• CacheControl.getCapacityLimit returns maximum weight correctly when weigher is present

This is a preview release for evaluation purposes and should not be used in production. The final release is planed as "Cogee Beach" - 2.6.0.Final.

Fixes and Improvements

• eternal(true/false) / MutableEntry.setExpiryTime: Expiry can be modified, although no other expiry setting is present, or in other words: the timer support is available by default. If eternal(true) is configured, timer support is disabled and Cache.invoke / MutableEntry.setExpiryTime or Cache.expireAt cannot be used
• Cache.invoke / MutableEntry.setExpiryTime: has no effect if entry is not existing
• Cache.invoke / MutableEntry.getExpiryTime always returns positive time value
• CI tests with Android API level 26 and API level 30
• Expiry: handle time values close to Long.MAX_VALUE without overflow, although the application should not produce these.
• Support Duration for duration parameters in the Cache2kBuilder
• Config section InternalConfig in cache2k-core for specific tuning values that should not be exposed in the public API
• Spring support: SpringCache2kDefaultSupplier provides default setup and manager context
• Spring support: SpringCache2kManager.setDefaultCacheNames() added
• Spring support: SpringCache2kManager.addCache(String, Function)
• Spring support: added SpringCache2kDefaultCustomizer
• Corrected signature BulkCacheLoader.BulkCallback.onLoadFailure(Set, Exception) to onLoadFailure(Iterable, Exception)

Possible breakages

Changes that may break existing applications.

• Spring support: SpringCache2kManager.defaultSetup throws IllegalStateException if not called before caches are added
• EXPIRY_NOT_ETERNAL constant removed from Cache2kConfig
• Fixed generic typing issues in org.cache2k.config package
• Sechduler.schedule uses delay duration instead of absolute time
• TimeReference.millis() renamed to ticks() and additional conversion methods to support
• other time resolutions than milliseconds
• Safety gap system property for sharp timeout changed to: org.cache2k.sharpExpirySafetyGapMillis
• Removed capability to modify internal constants via Tunable
• removed SpringCache2kCacheManager.setCaches(Collection<Cache2kConfig<?, ?>> cacheConfigurationList)

Non Functional Improvements

• Started with tests based on JUnit 5
• Documentation and examples for expiry, expiry policy
• Documentation improvements, fixed many typos and grammar errors in the API package

Credits

• Marcel Schnelle, mannodermaus for the contribution of Android CI tests, PR#178

This is a preview release for evaluation purposes and should not be used in production. The final release is planed as "Cogee Beach" - 2.6.0.Final.

Fixes and Improvements

• Documentation touch ups
• Cache disable support, Github issue #74
• Eviction improvements, minimal change to improve eviction, See issue comment
• Examples for expiry policy in ExpiryPolicyExampleTest unit test
• Idle scan: a more efficient expire after access / time to idle alternative, Github issue #39

This change log lists the changes since 2.4.0.Final.

Fixes and Improvements

• Improve exception handling when async callbacks are completed after the cache is closed, GH#175
• Fix wrong links to the documentation

Using this cache2k version

The binaries are available on maven central.

For Java SE/EE and Android environments

For Maven users:

    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>cache2k-api</artifactId>
      <version>2.4.1.Final</version>
    </dependency>
    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>cache2k-core</artifactId>
      <version>2.4.1.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

def cache2kVersion = '2.4.1.Final'

dependencies {
    implementation "org.cache2k:cache2k-api:${cache2kVersion}"
    runtimeOnly "org.cache2k:cache2k-core:${cache2kVersion}"
}

Note to Android users: The included jar files contain code that might only be needed in server environments (e.g. JMX support). It is possible to strip unnecessary code. Example ProGuard rules can be found at Andriod - cache2k User Guide

Using the JCache / JSR107 provider

Maven users include the cache2k JCache provider this way:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-jcache</artifactId>
      <version>2.4.1.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

dependencies {
    runtimeOnly "org.cache2k:cache2k-jcache:2.4.1.Final"
}

Implementation details, tuning tips and hints on configuration can be found at: JCache - cache2k User Guide

This change log lists the changes since 2.2.1.Final.

New and Noteworthy

This targets details to improve performance of big caches in multi core environments and minimizing the CPU impact on monitoring and frequent statistic polls.

Updated benchmarks comparing with Caffeine 3.0.4, and EHCache3 3.9.6

Fixes and Improvements

• Change default entry capacity to 1802. When the capacity is reported to a monitoring system or otherwise analysed, this serves as a magic number to indicate that the cache capacity is essentially not configured intentionally
• Improved hit counter accuracy for statistics, see: https://github.com/cache2k/cache2k/issues/150
• Improved statistics retrieval. When requesting the statistics, e.g. for micrometer export, no expensive operations are performed any more and no cache wide locking is done. In consequence statistics can be retrieved more frequently without big effect on the running application. Since there is no cache wide lock, statistics counters can have inconsistencies, e.g. the inserted and removed entries might not match exactly with the current size.
• Eviction throughput improvement. The Clock-Pro ghost/history table is limited to 3K entries. Profiling showed that the big ghost table attributed to lower performance with bigger cache sizes (1 million entries) and did not contribute significantly to a better hitrate.
• Various code quality improvements

API Breakages

• MutableCacheEntry.getValueOrNull: removed, since wrongly introduced in version 2.0.

Using this cache2k version

The binaries are available on maven central.

For Java SE/EE and Android environments

For Maven users:

    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>cache2k-api</artifactId>
      <version>2.4.0.Final</version>
    </dependency>
    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>cache2k-core</artifactId>
      <version>2.4.0.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

def cache2kVersion = '2.4.0.Final'

dependencies {
    implementation "org.cache2k:cache2k-api:${cache2kVersion}"
    runtimeOnly "org.cache2k:cache2k-core:${cache2kVersion}"
}

Note to Android users: The included jar files contain code that might only be needed in server environments (e.g. JMX support). It is possible to strip unnecessary code. Example ProGuard rules can be found at Andriod - cache2k User Guide

Using the JCache / JSR107 provider

Maven users include the cache2k JCache provider this way:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-jcache</artifactId>
      <version>2.4.0.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

dependencies {
    runtimeOnly "org.cache2k:cache2k-jcache:2.4.0.Final"
}

Implementation details, tuning tips and hints on configuration can be found at: [JCache - cache2k User Guide](https://cache2k.org/docs/latest/user-guide.html#jcache

This is a preview release for evaluation purposes and should not be used in production. The final release is planed as "Port Philip" - 2.4.0.Final.

Fixes and Improvements

• Improved hit counter accuracy for statistics, see: https://github.com/cache2k/cache2k/issues/150
• Improved statistics retrieval. When requesting the statistics, e.g. for micrometer export, no expensive operations are performed any more and no cache wide locking is done. In consequence statistics can be retrieved more frequently without big effect on the running application. Since there is no cache wide lock, statistics counters can have inconsistencies, e.g. the inserted and removed entries might not match exactly with the current size.
• Eviction throughput improvement. The Clock-Pro ghost/history table is limited to 3K entries. Profiling showed that the big ghost table attributed to lower performance with bigger cache sizes (1 million entries) and did not contribute significantly to a better hitrate.
• Various code quality improvements

This change log lists the changes since 2.2.0.Final.

Fixes and Improvements

• Cache.entries: throws IlliegalStateException if remove is called twice on the iterator.
• Cache.asMap: aligned to the map contract, equals, hashCode cooperate with arbitrary maps, toString is implemented identical to Java maps (e.g. HashMap)

Credits

Many thanks for the valuable input to the contributors of this release:

• Ben Manes, Ben Manes, #174

Using this cache2k version

The binaries are available on maven central.

For Java SE/EE and Android environments

For Maven users:

    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>cache2k-api</artifactId>
      <version>2.2.1.Final</version>
    </dependency>
    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>cache2k-core</artifactId>
      <version>2.2.1.Final</version>
      <scope>runtime</scope>
    </dependency>

Recommended for Gradle users:

def cache2kVersion = '2.2.1.Final'

dependencies {
    implementation "org.cache2k:cache2k-api:${cache2kVersion}"
    runtimeOnly "org.cache2k:cache2k-core:${cache2kVersion}"
}

Note to Android users: The included jar files contain code that might only be needed in server environments (e.g. JMX support). It is possible to strip unnecessary code. Example ProGuard rules can be found at Andriod - cache2k User Guide

Using the JCache / JSR107 provider

Maven users include the cache2k JCache provider this way:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-jcache</artifactId>
      <version>2.2.1.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

dependencies {
    runtimeOnly "org.cache2k:cache2k-jcache:2.2.1.Final"
}

Implementation details, tuning tips and hints on configuration can be found at: [JCache - cache2k User Guide](https://cache2k.org/docs/latest/user-guide.html#jcache

This change log lists the complete changes since the last stable version 2.0.0.Final.

New and Noteworthy

• Bulk support: New interfaces BulkCacheLoader and AsyncBulkCacheLoader which are used by the cache operations getAll, loadAll, reloadAll and invokeAll. The will get more optimizations and improvements in the next development releases. GH#166
• CoalescingBulkLoader: combines multiple requests into a bulk requests or limits bulk requests to a maximum size. Recommended when using a bulk loader and refresh ahead. The CoalescingBulkLoader resides in the separate jar cache2k-addon.

Possible Breakages

Deprecated methods were removed (see below).

API changes

• Improve API of Feature
• Async loader: add cache to the load context
• Remove deprecated org.cache2k.integration package
• Remove deprecated methods Cache.loadAll, Cache.reloadAll with CacheOperationCompletionListener
• Remove deprecated classes AdvancedKeyValueSource, KeyValueStore
• The deprecation flag for expireAt is removed. We keep this method
• Remove unused org.cache2k.spi.Cache2kExtensionProvider

Fixes and Improvements

• cache2k-api / Modules: export org.cache2k.annotation for Nullable etc. Improved new bulk loader support.
• Improve entry processor performance, GH#170
• Consistent exception handling for Cache.computeIfAbsent, GH#171
• Support for AutoClosable for async loaders
• Cache.asMap(): Align exception handling computeIfPresent, compute with ConcurrentMap contract

Credits

Many thanks for the valuable input to the contributors of this release:

• Fabrice Bacchella, fbacchella, #170
• Jingxiao GU, dawnwords, #171
• cybuch, cybuch, #166

Using this cache2k version

The binaries are available on maven central.

For Java SE/EE and Android environments

For Maven users:

    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>cache2k-api</artifactId>
      <version>2.2.0.Final</version>
    </dependency>
    <dependency>
      <groupId>${project.groupId}</groupId>
      <artifactId>cache2k-core</artifactId>
      <version>2.2.0.Final</version>
      <scope>runtime</scope>
    </dependency>

Recommended for Gradle users:

def cache2kVersion = '2.2.0.Final'

dependencies {
    implementation "org.cache2k:cache2k-api:${cache2kVersion}"
    runtimeOnly "org.cache2k:cache2k-core:${cache2kVersion}"
}

Note to Android users: The included jar files contain code that might only be needed in server environments (e.g. JMX support). It is possible to strip unnecessary code. Example ProGuard rules can be found at Andriod - cache2k User Guide

Using the JCache / JSR107 provider

Maven users include the cache2k JCache provider this way:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-jcache</artifactId>
      <version>2.2.0.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

dependencies {
    runtimeOnly "org.cache2k:cache2k-jcache:2.2.0.Final"
}

Implementation details, tuning tips and hints on configuration can be found at: [JCache - cache2k User Guide](https://cache2k.org/docs/latest/user-guide.html#jcache

This is a preview release for evaluation purposes and should not be used in production. The final release is planed as "Twofold Bay" - 2.2.0.Final.

Fixes and Improvements

Improved new bulk loader support.

• AsyncBulkCacheLoader.BulkCallback: New methods onLoadFailure(key, exception) and onLoadFailure(keys, exception)
• CoalescingBulkLoader: Fix/improve concurrency and exception handling

This is a preview release for evaluation purposes and should not be used in production. The final release is planed as "Twofold Bay" - 2.2.0.Final.

API changes

Remove deprecated API elements:

• org.cache2k.integration package
• Cache.loadAll, Cache.reloadAll with CacheOperationCompletionListener
• AdvancedKeyValueSource, KeyValueStore

This is a preview release for evaluation purposes and should not be used in production. The final release is planed as "Twofold Bay" - 2.2.0.Final.

New and Noteworthy

• Update bulk support: improve API, ensure basic functionality, concurrency tests, see GH#166

Fixes and Improvements

• Configuration of CoalescingBulkLoader
• Improve API of Feature
• Fix failure callback in bulk loader processing
• Documentation
• Async loader: add cache to the load context

This is a preview release for evaluation purposes and should not be used in production. The final release is planed as "Twofold Bay" - 2.2.0.Final.

New and Noteworthy

• Update bulk support: improve API, ensure basic functionality, concurrency tests, see GH#166

Fixes and Improvements

• Improve interface for bulk support
• Improve entry processor performance, GH#170
• Consistent exception handling for Cache.computeIfAbsent, GH#171
• Support for AutoClosable for async loaders
• Cache.asMap(): Align exception handling computeIfPresent, compute with ConcurrentMap contract

Credits

Many thanks to the contributors of this release:

• Fabrice Bacchella, fbacchella, #170
• Jingxiao GU, dawnwords, #171

This is a preview release for evaluation purposes and should not be used in production. The final release is planed as "Twofold Bay" - 2.2.0.Final.

New and Noteworthy

• Bulk support: New interfaces BulkCacheLoader and AsyncBulkCacheLoader which are used by the cache operations getAll, loadAll, reloadAll and invokeAll. The will get more optimizations and improvements in the next development releases. GH#166

Fixes and Improvements

• cache2k-api / Modules: export org.cache2k.annotation for Nullable etc.

This change log lists the changes since the last stable version 1.6.0.Final.

Upgrading from version 1

Version 2 has breaking changes. Recompilation is required. Most code will run with minor or no modifications. Common used functionality was kept or will be replaced gradually via deprecation. Deprecated elements may be removed in a version 2 minor release. Asses your code and change deprecated usages to the suggested alternative to be compatible with future releases.

Major changes:

• Requires at least Java 8 to run
• JMX and XML configuration support is no longer part of cache2k-core
• No caching of exceptions by default. This has to be enabled explicitly by specifying ResiliencePolicy. Previous default resilience available as UniversalResiliencePolicy in cache2k-addon

New and Noteworthy

cache2k now requires at least Java 8. This release focusses on API cleanup and touch ups with adaptions to available Java 8 concepts (e.g. CompletableFuture or Duration). No major functionality was added.

• cache2k-api, cache2k-core, cache2k-jmx and cache2k-config are fully modularized
• Requires at least Java 8 to run
• Adaptions to Java 8 on API level. E.g. use of Duration in the configuration
• New interfaces for CacheLoader and CacheWriter in package org.cache2k.io
• Removal of deprecated classes and methods
• JMX and XML configuration support is no longer part of cache2k-core
• OSGi support with cache2k-osgi-all removed, see: GH#83
• @Nullable annotations with Kotlin native type support
• General scheme to enable extra functionality (Feature), used for JMX and Micrometer support
• No caching of exceptions by default. This has to be enabled explicitly by specifying ResiliencePolicy. Previous default resilience available as UniversalResiliencePolicy in cache2k-addon
• Configuration: Functionality can be bundled in features and can augment the configuration and wrap the cache instance.

Possible Breakages

Since this is a major release, some rarely used things in the API are changed without backwards compatibility. Most code is supposed to run without breaking.

• Requires at least Java 8 to run
• Remove deprecated classes and methods: Cache.prefetch, Cache.prefetchAll, IntCache, LongCache, CacheEntry.getLastModification, AbstractCacheEntry
• Incompatible change of CustomizationSupplier interface
• org.cache2k.integration.ResiliencePolicy removed. Replaced by: org.cache2k.io.ResiliencePolicy
• JMX support moved from cache2k-core to cache2k-jmx to minimize module dependencies
• XML configuration moved from cache2k-core to cache2k-config to minimize module dependencies
• Dropped apache commons logging support. Commons logging seems to be not maintained any more and lacks Jigsaw/module support.
• Drop support for XML configuration on Android, removed XML pull dependency (The Android will be potentially unsupported in cache2k V2 at first)
• Moved JCache configuration classes in org.cache.jcache from cache2k-api to cache2k-jcache. If these are used, cache2k-jcache needs to be in compile scope.
• Cache2kConfiguration: Changed all parameters of type long, representing milliseconds to type Duration
• Remove deprecated classes and methods: Cache.prefetch, Cache.prefetchAll, IntCache, LongCache,, CacheEntry.getLastModification, AbstractCacheEntry
• Cache.getStatistics removed. Replaced by CacheManagement.of(Cache).sampleStatistics().
• Cache.clearAndClose removed. Replaced by CacheManagement.destroy
• Removed deprecated MutableCacheEntry.getCurrentTime, replaced with getStartTime
• Remove MutableCacheEntry.wasExisting and MutableCacheEntry.getOldValue
• Rename MutableCacheEntry.getRefreshedTime to getModificationTime
• MutableCacheEntry.exists: Does not change the value after setValue or triggered load
• MutableCacheEntry.getValue: Does not change the value after setValue
• Every class with Configuration shortened to Config and consequently changed the package name org.cache2k.configuration to org.cache2k.config.
• Cache2kBuilder.toConfiguration() renamed to config()
• Lots restructuring around the extra configuration sections and customizations
• remove Cache2kBuilder.enableJmx. Replaced with Cache2kBuilder.enable(JmxSupport.class)
• Cache.requestInterface throws UnsupportedOperationException if the requested interface is not supported instead of null
• Change in special expiry values semantics: ExpiryTimeValues.NO_CACHE removed. ExpiryTimeValues.NOW does not start a refresh and expire immediately. ExpiryTimeValues.REFRESH does expire and start a refresh if refresh ahead is enabled.
• No caching of exceptions by default. This has to be enabled explicitly by specifying ResiliencePolicy. Previous default resilience available as UniversalResiliencePolicy in cache2k-addon
• Move Weigher to package org.cache2k.operation.
• Rename MutableCacheEntry.reload to MutableCacheEntry.load
• Remove Cache2kBuilder.enableJmx

API Changes

• org.cache2k.integration.CacheLoader and everything in package org.cache2k.integration is deprecated. Replacements are available in org.cache2k.io. This major change was done to change from abstract classes to interface. The new package was introduced for smoother transition to keep the previous classes and deprecated them.
• Move TimeReference to org.cache2k.operation and also make Scheduler available
• Cache2kBuilder: New methods setup and enable
• New method: Cache.computeIfAbsent with function
• New methods Cache.loadAll and Cache.reloadAll which return CompletableFuture Old methods which use CacheOperationCompletionListener are deprecated
• New methods: Cache.mutate, Cache.mutateAll for a mutation only entry processor variant
• Cache.entries and Cache.keys return a Set for iteration and stream support
• New method CacheEntry.getExceptionInfo()
• org.cache2k.jmx, API for JMX MXBeans removed
• New interfaces CacheOperation, CacheControl and CacheInfo in org.cache2k.operation
• New method: MutableCacheEntry.getExpiryTime()
• New method: MutableCacheEntry.setExpiryTime()
• New method: MutableCacheEntry.lock
• Lots of generic typing refinements
• Allow listeners to throw a checked exception
• @Nullable, @NonNull annotations
• Deprecated AdvancedKeyValueSource and KeyValueStore

Fixes and Improvements

• All cache customizations (e.g. CacheLoader) implement Customization.
• Speedup of internal hash table, because compatibility for Java 6 could be removed
• Cache.loadAll() and Cache.reloadAll() complete with exception if a a loader exception happened. If more than one exception happened the one is propagated.
• Improved interface of ExceptionPropagator and LoadExceptionInfo
• Cache.invoke, EntryProcessor: Make expiry calculations and listeners calls more consistent if expiry event races with the start of the operation
• MutableCacheEntry.lock allows to lock an entry for mutation explicitly
• Cache.asMap / ConcurrentMap implementation implements compute methods and runs them only once
• Introduced ConfigAugmenter which can make changed to the configuration before a cache is build
• Cache2kBuilder: Methods setup, apply allow to execute a function on the configuration or builder, which can be used to factor out configuration fragments. We use this to provide enable and disable methods on policies.
• AdvancedCacheLoader, AsyncCacheLoader and ExpiryPolicy get null if current entry carries exception, https://github.com/cache2k/cache2k/issues/163
• Remove ServiceLoader in modules cache2k-jmx and cache2k-micrometer
• Introduce concept of CacheFeature and ToggleCacheFeature
• CacheType: immutable instead of bean. CacheType.of moved from CacheTypeCapture
• Remove the need of serializable from the configuration objects, by doing a deep copy of the default configuration via bean setters and getters.
• Cache2kConfig: Make setEternal a separate flag. Remove logic from setters, so we can use setters and getter to copy the object
• Ignore entryCapacity setting in case a weigher is specified
• Cap suppression or caching of exceptions determined by ResiliencePolicy to the expireAfterWrite duration, if specified
• Fix site build for Java 11
• Documentation touch ups
• Change configuration XML schema to version 2 and archive version 1
• Spring cache manager applies default setup also to dynamically created caches that are retrieved via getCache

Using this cache2k version

The binaries are available on maven central.

For Java SE/EE and Android environments

For Maven users:

   ​<properties>
     ​<cache2k-version>2.0.0.Final</cache2k-version>
   ​</properties>
   ​<dependency>
     ​<groupId>org.cache2k</groupId>
     ​<artifactId>cache2k-api</artifactId>
     ​<version>${cache2k-version}</version>
   ​</dependency>
   ​<dependency>
     ​<groupId>org.cache2k</groupId>
     ​<artifactId>cache2k-core</artifactId>
     ​<version>${cache2k-version}</version>
     ​<scope>runtime</scope>
   ​</dependency>

Recommended for Gradle users:

def cache2kVersion = '2.0.0.Final'

dependencies {
    implementation "org.cache2k:cache2k-api:${cache2kVersion}"
    runtimeOnly "org.cache2k:cache2k-core:${cache2kVersion}"
}

For the first steps look at Getting Started - cache2k User Guide

Using the JCache / JSR107 provider

Maven users include the cache2k JCache provider this way:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-jcache</artifactId>
      <version>2.0.0.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

dependencies {
    runtimeOnly "org.cache2k:cache2k-jcache:2.0.0.Final"
}

Implementation details, tuning tips and hints on configuration can be found at: JCache - cache2k User Guide

This is a preview release for evaluation purposes and should not be used in production.

The preview is in preparation for version 2 which will have some major breaking changes to the previous releases. The final release will be 2.0.0.Final - "North Atlantic".

Fixes and Improvements

• Documentation updates
• Spring cache manager applies default setup also to dynamically created caches that are retrieved via getCache.

This is a preview release for evaluation purposes and should not be used in production.

The preview is in preparation for version 2 which will have some major breaking changes to the previous releases. The final release will be 2.0.0.Final - "North Atlantic".

New and Noteworthy

• Documentation fixes. This is the release candidate 2 of cache2k version 2.0

API Changes Possible Breakages

• Move Weigher to package org.cache2k.operation.

Fixes and Improvements

• Fix site build for Java 11
• Documentation touch ups
• Change configuration XML schema to version 2 and archive version 1
• Event listeners will be send the wrapped cache

This is a preview release for evaluation purposes and should not be used in production.

The preview is in preparation for version 2 which will have some major breaking changes to the previous releases. The final release will be 2.0.0.Final - "North Atlantic".

New and Noteworthy

• Last set of API changes. This is the release candidate 1 of cache2k version 2.0

Possible Breakages

• N/A

API Changes Possible Breakages

• Customizations can implement AutoCloseable, changed from Closeable, Java 8 improvement
• Cache and CacheManager implements AutoCloseable, changed from Closeable, Java 8 improvement
• Scheduler and TimeReference available in base configuration and API

Fixes and Improvements

• Common timer threads are destroyed when last cache is closed, []GH#167](https://github.com/cache2k/cache2k/issues/167), Thanks Jingxiao Gu / @dawnwords for reporting!
• Corner case: Don't drop a altered default name after all cache managers are closed

This is a preview release for evaluation purposes and should not be used in production.

The preview is in preparation for version 2 which will have some major breaking changes to the previous releases. The final release will be 2.0.0.Final - "North Atlantic".

New and Noteworthy

• Update to enhance compatibility of client code between version 1.6 with 2.0 of cache2k

API Changes / Possible Breakages

• Within alpha: Un deprecate KeyValueSource, that's simple and useful
• Drop ExpiryTimeValues.NO_CACHE. ExpiryTimeValues.NOW which has a value of 0 means no caching, and does not start a refresh. Introduced ExpiryTimeValues.REFRESH again, sinc logically everything between 0 (exclusive) and the current time, expires and starts a refresh, if refresh ahead is enabled.
• Within alpha: Reverse hierarchy for new CacheLoaderException, which enhanced compatibility with code doing an instanceof

Fixes and Improvements

• Cap suppression or caching of exceptions determined by ResiliencePolicy to the expireAfterWrite duration, if specified

This is a preview release for evaluation purposes and should not be used in production.

The preview is in preparation for version 2 which will have some major breaking changes to the previous releases. The final release will be 2.0.0.Final - "North Atlantic".

New and Noteworthy

• @Nullable annotations
• General scheme to enable extra functionality, used for JMX and Micrometer support
• No caching of exceptions by default. This has to be enabled explicitly by specifying ResiliencePolicy. Previous default resilience available as UniversalResiliencePolicy in cache2k-addon

Possible Breakages

Since this is a major release, some rarely used things in the API are changed without backwards compatibility. Most code is supposed to run without breaking.

• Cache.getStatistics removed. Replaced by CacheManagement.of(Cache).sampleStatistics().
• Cache.clearAndClose removed. Replaced by CacheManagement.destroy
• Removed deprecated MutableCacheEntry.getCurrentTime, replaced with getStartTime
• Remove MutableCacheEntry.wasExisting and MutableCacheEntry.getOldValue
• Rename MutableCacheEntry.getRefreshedTime to getModificationTime
• MutableCacheEntry.exists: Does not change the value after setValue or triggered load
• MutableCacheEntry.getValue: Does not change the value after setValue
• Every class with Configuration shortened to Config and consequently changed the package name org.cache2k.configuration to org.cache2k.config.
• Cache2kBuilder.toConfiguration() renamed to config()
• Lots restructuring around the extra configuration sections and customizations
• remove Cache2kBuilder.enableJmx. Replaced with Cache2kBuilder.enable(JmxSupport.class)
• Cache.requestInterface throws UnsupportedOperationException if the requested interface is not supported instead of null
• Change in special expiry values semantics: Remove ExpiryTimeValues.REFRESH. ExpiryTimeValues.NOW expires and starts a refresh if refresh ahead is enabled. ExpiryTimeValues.NO_CACHE expires and starts no refresh.
• No caching of exceptions by default. This has to be enabled explicitly by specifying ResiliencePolicy. Previous default resilience available as UniversalResiliencePolicy in cache2k-addon

API Changes

• Renamed ExceptionInformation to LoadExceptionInfo
• New method CacheEntry.getExceptionInfo()
• org.cache2k.jmx, API for JMX MXBeans removed
• New interfaces CacheManagement, CacheControl and CacheInfo in org.cache2k.management
• New method: MutableCacheEntry.lock
• Rename MutableCacheEntry.reload to MutableCacheEntry.load
• Remove TimeReference interface from public API and make that local to cache2k-core
• New method: MutableCacheEntry.getExpiryTime()
• Remove Cache2kBuilder.enableJmx
• Cache2kBuilder: New methods `set
• New methods: Cache.mutate, Cache.mutateAll

Fixes and Improvements

• Cache.loadAll() and Cache.reloadAll() complete with exception if a a loader exception happened. If more than one exception happened the one is propagated.
• Improved interface of ExceptionPropagator and LoadExceptionInfo, A CacheEntry may be cast to LoadExceptionInfo if an exception is present
• Cache.invoke, EntryProcessor: Make expiry calculations and listeners calls more consistent if expiry event races with the start of the operation
• MutableCacheEntry.lock allows to lock an entry for mutation explicitly
• Cache.asMap / ConcurrentMap implementation implements compute methods and runs them only once
• Introduced ConfigAugmenter which can make changed to the configuration before a cache is build
• Cache2kBuilder: Methods setup, apply allow to execute a function on the configuration or builder, which can be used to factor out configuration fragments. We use this to provide enable and disable methods on policies.
• AdvancedCacheLoader, AsyncCacheLoader and ExpiryPolicy get null if current entry carries exception, https://github.com/cache2k/cache2k/issues/163
• Remove ServiceLoader from JMX support in cache2k-jmx, cache2k-micrometer
• Introduce concept of CacheFeature and ToggleCacheFeature
• CacheType: immutable instead of bean. CacheType.of moved from CacheTypeCapture
• Remove the need of serializable from the configuration objects, by doing a deep copy of the default configuration via bean setters and getters.
• Cache2kConfig: Make setEternal a separate flag. Remove logic from setters, so we can use setters and getter to copy the object
• Cache.mutate, Cache.mutateAll for a mutation only entry processor variant
• @Nullable, @NonNull annotations
• Within alpha: change new ExceptionPropagator from <K> to <K, V>, dito at LoadExceptionInfo
• @Nullness annotations
• Lots of typing refinements
• Cache.entries and Cache.keys return a Set
• Cache.computeIfAbsent with function
• Ignore entryCapacity setting in case a weigher is specified
• Allow listeners to throw a checked exception

This is a preview release for evaluation purposes and should not be used in production.

The preview is in preparation for version 2 which will have some major breaking changes to the previous releases. The final release will be 2.0.0.Final - "North Atlantic".

New and Noteworthy

• cache2k-api, cache2k-core, cache2k-jmx and cache2k-config are fully modularized
• Requires at least Java 8 to run
• Adaptions to Java 8 on API level. E.g. use of Duration in the configuration
• New interfaces for CacheLoader and CacheWriter
• Removal of deprecated classes and methods
• JMX and XML configuration support is no longer part of cache2k-core
• OSGi support with cache2k-osgi-all removed, see: https://github.com/cache2k/cache2k/issues/83

Possible Breakages

Since this is a major release, some rarely used things in the API are changed without backwards compatibility. Most code is supposed to run without breaking.

• Requires at least Java 8 to run
• Remove deprecated classes and methods: Cache.prefetch, Cache.prefetchAll, IntCache, LongCache, CacheEntry.getLastModification, AbstractCacheEntry
• Incompatible change of CustomizationSupplier interface
• org.cache2k.integration.ResiliencePolicy removed. Replaced by: org.cache2k.io.ResiliencePolicy
• JMX support moved from cache2k-core to cache2k-jmx to minimize module dependencies
• XML configuration moved from cache2k-core to cache2k-config to minimize module dependencies
• Dropped apache commons logging support. Commons logging seems to be not maintained any more and lacks Jigsaw/module support.
• Drop support for XML configuration on Android, removed XML pull dependency (The Android will be potentially unsupported in cache2k V2 at first)
• Moved JCache configuration classes in org.cache.jcache from cache2k-api to cache2k-jcache. If these are used, cache2k-jcache needs to be in compile scope.
• Cache2kConfiguration: Changed all parameters of type long, representing milliseconds to type Duration

API Changes

• org.cache2k.integration.CacheLoader and everything in package org.cache2k.integration is deprecated. Replacements are available in org.cache2k.io. This major change was done to change from abstract classes to interface. The new package was introduced for smoother transition to keep the previous classes and deprecated them.
• Add Cache.loadAll and Cache.reloadAll which return CompletableFuture Old methods which use CacheOperationCompletionListener are deprecated
• Remove deprecated classes and methods: Cache.prefetch, Cache.prefetchAll, IntCache, LongCache, CacheEntry.getLastModification, AbstractCacheEntry

Fixes and Improvements

• All cache customizations (e.g. CacheLoader) implement Customization.
• Speedup of internal hash table, because compatibility for Java 6 could be removed

cache2k is a high performance and light weight in-process caching library. Compared to other libraries (EHCache, Guava and Caffeine) it achieves the highest throughput for cache hits while still providing one of the best eviction efficiency. Advanced features of cache2k, like refresh ahead and resilience can solve typical application problems with ease.

This change log lists the complete changes since the last stable version 1.4.1.Final.

New and Noteworthy

• New timer based on hierarchical timer wheels, which is more performance and scales linear with more cache entries
• No more extra thread per cache, in cache timer is used, e.g. for expiry

Potential breakages

• No separate executor for async listeners by default any more. If an async listener executor is not specified it uses the executor defined by Cache2kBuilder.executor which in turn defaults to the common ForkJoinPool in Java 8.
• Slightly more lag for operations triggered by time, e.g. cache cleanup after expiry, calls of expiry listeners, refreshing. The lag can be controlled by Cache2kBuilder.timerLag

API Changes

• Deprecated ExpiryTimeValues.NO_CACHE
• Deprecated Cache2kBuilder.prefetchExecutor, introduced Cache2kBuilder.refreshExecutor (rename)
• Deprecated Cache.prefetch and Cache.prefetchAll

Fixes and Improvements

• Remove hash quality metric
• MutableCacheEntry.reload() does load the entry even if already cached
• After recovering from a load exception the expiry policy did not see the correct previous entry value with the exception
• Improved internal structure and test coverage

Using this cache2k version

The binaries are available on maven central.

For Java SE/EE and Android environments

For Maven users:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-base-pom</artifactId>
      <version>1.6.0.Final</version>
      <type>pom</type>
    </dependency>

Recommended for Gradle users:

def cache2kVersion = '1.6.0.Final'

dependencies {
    implementation "org.cache2k:cache2k-api:${cache2kVersion}"
    runtimeOnly "org.cache2k:cache2k-core:${cache2kVersion}"
}

Note to Android users: The included jar files contain code that might only be needed in server environments (e.g. JMX support). It is possible to strip unnecessary code. Example ProGuard rules can be found at Andriod - cache2k User Guide

Using the JCache / JSR107 provider

Maven users include the cache2k JCache provider this way:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-jcache</artifactId>
      <version>1.6.0.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

dependencies {
    runtimeOnly "org.cache2k:cache2k-jcache:1.6.0.Final"
}

Implementation details, tuning tips and hints on configuration can be found at: [JCache - cache2k User Guide](https://cache2k.org/docs/latest/user-guide.html#jcache

This is a preview release for evaluation purposes and should not be used in production. The final release is planed as "Gulf of Thailand 1.6.0.Final".

New and Noteworthy

• N/A

Possible Breakages

• N/A

API Changes

• Deprecated Cache.prefetch and Cache.prefetchAll

Fixes and Improvements

• After recovering from a load exception the expiry policy did not see the correct previous entry value with the exception
• Improved internal structure and test coverage

This is a preview release for evaluation purposes and should not be used in production. The final release is planed as "Gulf of Thailand 1.6.0.Final".

New and Noteworthy

• New timer based on hierarchical timer wheels, which is more performance and scales linear with more cache entries
• No more extra thread per cache, in cache timer is used, e.g. for expiry

Possible Breakages

• No separate executor for async listeners by default any more. If an async listener executor is not specified it uses the executor defined by Cache2kBuilder.executor which in turn defaults to the common ForkJoinPool in Java 8.
• Slightly more lag for operations triggered by time, e.g. cache cleanup after expiry, calls of expiry listeners, refreshing. The lag can be controlled by Cache2kBuilder.timerLag

API Changes

• Deprecated ExpiryTimeValues.NO_CACHE
• Deprecated Cache2kBuilder.prefetchExecutor, introduced Cache2kBuilder.refreshExecutor (rename)

Fixes and Improvements

• Remove hash quality metric
• MutableCacheEntry.reload() does load the entry even if already cached

cache2k is a high performance and light weight in-process caching library. Compared to other libraries (EHCache, Guava and Caffeine) it achieves the highest throughput for cache hits while still providing one of the best eviction efficiency. Advanced features of cache2k, like refresh ahead and resilience can solve typical application problems with ease.

Critical bug fix for 1.4.0.Final.

Fixes

• Race under special conditions in Cache.computeIfAbsent, Cache.peekAndPut, Cache.get with loader. See: https://github.com/cache2k/cache2k/issues/155

Using this cache2k version

The binaries are available on maven central.

For Java SE/EE and Android environments

For Maven users:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-base-pom</artifactId>
      <version>1.4.1.Final</version>
      <type>pom</type>
    </dependency>

Recommended for Gradle users:

def cache2kVersion = '1.4.1.Final'

dependencies {
    implementation "org.cache2k:cache2k-api:${cache2kVersion}"
    runtimeOnly "org.cache2k:cache2k-core:${cache2kVersion}"
}

Note to Android users: The included jar files contain code that might only be needed in server environments (e.g. JMX support). It is possible to strip unnecessary code. Example ProGuard rules can be found at Andriod - cache2k User Guide

Using the JCache / JSR107 provider

Maven users include the cache2k JCache provider this way:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-jcache</artifactId>
      <version>1.4.1.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

dependencies {
    runtimeOnly "org.cache2k:cache2k-jcache:1.4.1.Final"
}

Implementation details, tuning tips and hints on configuration can be found at: JCache - cache2k User Guide

cache2k is a high performance and light weight in-process caching library. Compared to other libraries (EHCache, Guava and Caffeine) it achieves the highest throughput for cache hits while still providing one of the best eviction efficiency. Advanced features of cache2k, like refresh ahead and resilience can solve typical application problems with ease.

This change log lists the complete changes since the last stable version 1.2.4.Final.

New and Noteworthy

• Weigher
• AsyncCacheLoader
• Eviction listener and eviction improvements
• Synchronous execution of expiry listener
• Micrometer support
• Online resize of caches
• Support for GraalVM native image build

API Changes

New methods / fields:

• CacheManager.STANDARD_DEFAULT_MANAGER_NAME
• CacheInfoMXBean.isWeigherPresent()
• CacheInfoMXBean.isLoaderPresent()
• CacheInfoMXBean.getTotalWeight()
• CacheInfoMXBean.getMaximumWeight()
• CacheInfoMXBean.getCapacityLimit()
• Cache.getStatistics()

New interface:

• AsyncCacheLoader

Deprecation:

• IntCache, LongCache
• Cache2kBuilder.buildIntCache(), Cache2kBuilder.buildLongCache()

API Changes and Potential breakages

Cache2kBuilder.addListener will execute an EntryExpiredLister synchronously. In version 1.2 an expiry listener was always executed asynchronously. This is an potentially incompatible change, in case expiry listeners are used. Review the existing client code and make sure that addAsyncListeners is used for an EntryExpiredLister if that is wanted.

Fixes

• Fix CacheManager.setDefaultName, see GH#108
• race of refresh and delete: if an entry is deleted via Cache.remove it was not reappearing when refreshed concurrently
• fix missing expiry listener call after a created listener call, in case expiry during the insert
• expiry, expireAfterWrite, refreshAhead: Fix race condition of a Cache.put and the

Improvements

• Remove randomized hash seed and simplify the "rehashing" of hash codes identical to Java HashMap and ConcurrentHashMap
• Async Cacheloader GH#93
• CacheEntryEvictionListener added, GH#59
• Expose cache statistics via Cache.getStatistics()
• Eviction: Efficiency improvements, see comment: https://github.com/cache2k/cache2k/issues/101#issuecomment-523003823
• Expiry listener supports synchronous operation
• Deprecated IntCache and LongCache
• Internal: Improvement and simplification of ExceptionPropagator handling termination of the probation period after a refresh.
• Cache.invoke / EntryProcessor: Internal improvements when using listeners: avoid unnecessary entry reads
• internal cleanup: use common code for refresh in different cache variants
• eviction efficiency fix for a few special short traces
• Support for new cache methods from Spring Framework 5.2
• doc clarifications and improvements
• SpringCache2kCacheManager.setAllowUnknownCache is true by default, to minimize initial setup
• CacheEntry.toString output does not call toString on the value and print hashCode instead
• doc clarifications
• Code style improvements

Using this cache2k version

The binaries are available on maven central.

For Java SE/EE and Android environments

For Maven users:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-base-pom</artifactId>
      <version>1.4.0.Final</version>
      <type>pom</type>
    </dependency>

Recommended for Gradle users:

def cache2kVersion = '1.4.0.Final'

dependencies {
    implementation "org.cache2k:cache2k-api:${cache2kVersion}"
    runtimeOnly "org.cache2k:cache2k-core:${cache2kVersion}"
}

Note to Android users: The included jar files contain code that might only be needed in server environments (e.g. JMX support). It is possible to strip unnecessary code. Example ProGuard rules can be found at Andriod - cache2k User Guide

Using the JCache / JSR107 provider

Maven users include the cache2k JCache provider this way:

    <dependency>
      <groupId>org.cache2k</groupId>
      <artifactId>cache2k-jcache</artifactId>
      <version>1.4.0.Final</version>
      <scope>runtime</scope>
    </dependency>

For Gradle users:

dependencies {
    runtimeOnly "org.cache2k:cache2k-jcache:1.4.0.Final"
}

Implementation details, tuning tips and hints on configuration can be found at: JCache - cache2k User Guide

This is a preview release for evaluation purposes and should not be used in production.

New and Noteworthy

• Stabilizing new features

Possible Breakages

• A created SpringCache2kCacheManager binds to the cache2k cache manager springDefault instead to default.

API Changes

• N/A

Fixes and Improvements

• Micrometer support: don't register to any registry by default
• Clarify semantics of current entry for AdvancedCacheLoader and AsyncCacheLoader

This is a preview release for evaluation purposes and should not be used in production.

New and Noteworthy

• Stabilizing new features

Possible Breakages

• N/A

API Changes

• N/A

Fixes and Improvements

• Fix corrupted JSON file for GraalVM native image build in last release

This is a preview release for evaluation purposes and should not be used in production.

New and Noteworthy

• Stabilizing new features

Possible Breakages

• N/A

API Changes

• N/A

Fixes and Improvements

• Improved GraalVM native image support, no extra configuration needed, https://github.com/cache2k/cache2k/issues/152
• Correct wrong EntryProcessor behavior introduced during version 1.3.x