Download JAR files tagged by used with all dependencies

# 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)

Pdf2Dom is a PDF parser that converts the documents to a HTML DOM representation. The obtained DOM tree may be then serialized to a HTML file or further processed. The inline CSS definitions contained in the resulting document are used for making the HTML page as similar as possible to the PDF input. A command-line utility for converting the PDF documents to HTML is included in the distribution package. Pdf2Dom may be also used as an independent Java library with a standard DOM interface for your DOM-based applications or as an alternative parser for the CSSBox rendering engine in order to add the PDF processing capability to CSSBox.

Jadex XML is an XML data binding framework for Java and also for other representations. The main idea of Jadex XML is that neither the XML-Schema on the one side nor the Java classes on the other side should define other binding. Instead, a separate mapping between both is used as a mediation. This allows designing the XML representation independent of the Java side but still being able to connect both as desired. This idea was first put forward by the JiBX data binding framework. Jadex XML pushes it further by combining it with the configuration by exception principle. The framework can detect obvious correspondences between both sides automatically and only needs configuration information when translations are necessary. The configuration information is currently specified directly in form of Java configuration classes.

Leveraging Tencent's 21 years of experience in network and audio/video technologies, Tencent Real-Time Communication (TRTC) offers multi-person audio/video calls and low-latency interactive live streaming solutions. With TRTC, you can quickly develop cost-effective, low-latency, and high-quality interactive audio/video services. Audio/Video Call Solution TRTC provides a client SDK that works across platforms and regions. This solution can be easily used on webpages to enable audio and video call capability for all applications. Low-Latency Interactive Live Streaming Solution TRTC leverages Tencent Cloud's high-quality node resources, industry-leading network and audio/video technologies to helps you build interactive live streaming services with minimal lags and a latency below 1 second, taking live streaming into the era of CDN 2.0.腾讯实时音视频（Tencent Real-Time Communication，TRTC）将腾讯21年来在网络与音视频技术上的深度积累，以多人音视频通话和低延时互动直播两大场景化方案，通过腾讯云服务向开发者开放，致力于帮助开发者快速搭建低成本、低延时、高品质的音视频互动解决方案。

ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications. Each time they are implemented there is a lot of work that goes into fixing the bugs and race conditions that are inevitable. Because of the difficulty of implementing these kinds of services, applications initially usually skimp on them ,which make them brittle in the presence of change and difficult to manage. Even when done correctly, different implementations of these services lead to management complexity when the applications are deployed.

Test Drop-in Framework for Selenium WebDriver 4.1.x This repository contains these major deliverables: a) the Test Drop-in Framework, b) a WebDriver implementation offering enhanced logging capabilities, and c) the @FindByJS annotation support Provides a thin abstraction layer between the test environment and the test class plus its helpers. This makes the test code independent of the test environment, thus allowing exchange of tests between organizations or even companies. It comes with an event firing WebDriver wrapper plus corresponding interface. This allows you to implement listeners to arbitrary WebDriver activities for various purposes such as logging. Offers support of JavaScript commands to find elements in a way similar to @FindBy used on fields in Page Object classes.

The Systems Biology Simulation Core Library provides an efficient and exhaustive Java™ implementation of methods to interpret the content of models encoded in the Systems Biology Markup Language (SBML) and its numerical solution. This library is based on the JSBML project. It can be used on every operating system for which a Java Virtual Machine is available. Version 2.0 and beyond support simulation in three frameworks: constraint-based analysis, stochastic simulation, and ordinary differential equation systems. SBSCL supports SED-ML and COMBINE archives in OMEX format.

This module groups all different output writers. Different output writers have different dependencies. To ensure that those dependencies do not leak to other output writer, or that we can limit to number of dependencies at runtime, output writers are split into separate modules based on the dependencies they use. For example, the CloudWatch output writers depends on the AWS SDK, which is quite large and not used by any other output writer. If you only want to send metrics to Graphite, there should be no need to have the AWS SDK in your classpath at runtime. Some dependencies are also problematic. They can introduce incompatibilities. For example, a few writers are based directly on log4j or logback. This direct dependence breaks the use of SLF4J. By isolating those output writers to a specific module, we can ensure this has minimal impact.