Download JAR files tagged by central with all dependencies

DefaultJ is a powerful Java library that provides default values for any class, offering multiple strategies for obtaining those values. It can be used as a dependency injection utility, similar to Guice. With 14 built-in strategies, DefaultJ can obtain default values through various means such as explicit bindings, annotations, enum values, factory methods, and more. It also supports custom annotations and offers annotation processors for validation. Available on Maven Central, DefaultJ can be easily integrated into Gradle and Maven projects. Contributions and selective usage of the library are encouraged.

# heatshrink-java Java library used to encode/decode [heatshrink](https://github.com/atomicobject/heatshrink) compressed data. ## Building ```bash ./gradlew build ``` ## Gradle dependency See https://search.maven.org/artifact/io.github.markrileybot/heatshrink-java/ ## Usage ### Java library ```java int windowSize = 9; int lookaheadSize = 8; ByteArrayOutputStream baos = new ByteArrayOutputStream(); try(HsOutputStream out = new HsOutputStream(baos, windowSize, lookaheadSize)) { out.write("ABCABCABCABCABCABC".getBytes()); } try(HsInputStream hsi = new HsInputStream(new ByteArrayInutStream(baos.toByteArray()), windowSize, lookaheadSize)) { byte[] res = new byte[512]; int len = hsi.read(res); System.out.println(new String(res, 0, len)); } ``` ### CLI ```bash $ java -jar heatshrink-java-exe.jar [-h] [-e|-d] [-v] [-w SIZE] [-l BITS] [IN_FILE] [OUT_FILE] ``` ## Status [](https://github.com/markrileybot/heatshrink-java/actions/workflows/gradle-publish.yml) [](https://coveralls.io/github/markrileybot/heatshrink-java?branch=master) [](https://maven-badges.herokuapp.com/maven-central/io.github.markrileybot/geokey)

A Java component which displays bytes in Hex- and ASCII-format. The component is designed as a standalone lib. A complete interface which provides the function of an HexEditor based on this lib exisits under the Fork of this project. \r\n This library is simply taken directly from sourceforge at https://sourceforge.net/projects/hexlib/ and made it available in maven central repository. No other changes have been made (including keeping the same license).

The Infinispan Spring Integration project provides Spring integration for Infinispan, a high performance distributed cache. Its primary features are * An implementation of org.springframework.cache.CacheManager, Spring's central caching abstraction, backed by Infinispan's EmbeddedCacheManager. To be used if your Spring-powered application and Infinispan are colocated, i.e. running within the same VM. * An implementation of org.springframework.cache.CacheManager backed by Infinispan's RemoteCacheManager. To bes used if your Spring-powered application accesses Infinispan remotely, i.e. over the network. * An implementation of org.springframework.cache.CacheManager backed by a CacheContainer reference. To be used if your Spring- powered application needs access to a CacheContainer defined outside the application (e.g. retrieved from JNDI) * Spring namespace support allowing shortcut definitions for all the components above In addition, Infinispan Spring Integration offers various FactoryBeans for facilitating creation of Infinispan core classes - Cache, CacheManager, ... - within a Spring context.

This API is a java library for various project scopes. Currently, it has worked in picture editors, and small applets. It can be deployed on all big three platforms : Windows, OSX and Linux. Originally, the file cache manager was the most important feature and the reason for what it was published. It becomes handful to handle heap memory before it overflows by appropriately using it (see javadoc). The new implementation lays on Maven Central repository and can be used as a dependency in a common Web Application (Java EE).

This module packages a circuit breaker that can be used to avoid overloading or otherwise depending on a temporarily unavailable (remote) system. The central use of the circuit breaker is to prevent failures from one system to cascade to other systems in an unchecked manner. Thus, our implementation is chiefly concerned with replacing a failing component with another component that fails in a very predictable manner. These failures are not "dropped" or otherwise made invisible, and still need to be handled, but they will occur in a predictable, and hopefully usable manner.