Java:packages

Factory Java packages

This is the Java:packages project. Its main purpose is to serve as development project for packages around the topic of Java in the openSUSE:Factory distribution. This project also provides *unofficial* backports of newest packages to current latest openSUSE release. The packages are *not* tested and might randomly break https://download.opensuse.org/repositories/Java:/packages/openSUSE_Factory_RISCV/ openSUSE:Factory:RISCV

openSUSE Factory Port for RISC-V

This is a project clone to build openSUSE:Factory for the RISC-V architecture. https://download.opensuse.org/repositories/openSUSE:/Factory:/RISCV/standard/ openSUSE:Factory

The next openSUSE distribution

openSUSE Tumbleweed: The Bleeding Edge, Perfected. Tumbleweed is the ultimate rolling release distribution, providing the latest software as it’s released, built upon a foundation of world-class stability and testing. * Always Current: Get the newest kernel, IDEs, desktops, and applications automatically. * Powerfully Stable: Experience the velocity of a rolling release without sacrificing the reliability you depend on. * Engineered for Professionals: The top choice for Developers, Power Users, and openSUSE Contributors who need the best tools for the job. If you demand the latest stable software, your choice is Tumbleweed. Staging dashboard is located at: https://build.opensuse.org/staging_workflows/openSUSE:Factory List of known devel projects: https://build.opensuse.org/package/view_file/openSUSE:Factory:Staging/dashboard/devel_projects Have a look at http://en.opensuse.org/Portal:Factory for more details. https://download.opensuse.org/repositories/openSUSE:/Factory/ports/ caffeine

High performance, near optimal caching library based on Java 8

A Cache is similar to ConcurrentMap, but not quite the same. The most fundamental difference is that a ConcurrentMap persists all elements that are added to it until they are explicitly removed. A Cache on the other hand is generally configured to evict entries automatically, in order to constrain its memory footprint. In some cases a LoadingCache or AsyncLoadingCache can be useful even if it doesn't evict entries, due to its automatic cache loading. Caffeine provide flexible construction to create a cache with a combination of the following features: automatic loading of entries into the cache, optionally asynchronously size-based eviction when a maximum is exceeded based on frequency and recency time-based expiration of entries, measured since last access or last write asynchronously refresh when the first stale request for an entry occurs keys automatically wrapped in weak references values automatically wrapped in weak or soft references notification of evicted (or otherwise removed) entries writes propagated to an external resource accumulation of cache access statistics