Download JAR files tagged by system with all dependencies

Semantic Turkey parent project. It contains the three modules about: core business logic, core services and firefox extension (ui and client in general) of the system. Three additional modules provide an implementation for the ontology manager to be bundled with the tool, an applet for graph visualization of ontologies and concept schemes and a test suite to run tests on a java client framework. An ANT build file allows to package the xpi for Firefox installation (read README2BUILD.TXT file for info)

The Polymorphic DSL test framework was designed to solve the challenges with testing large, complex systems. Modern architecture requires software to run as distrubited systems or on multiple platforms. The conventional cost of testing these systems is quite high. PDSL allows a user to describe the system under test using a DSL of some kind: a picture, sentences in natural languages, graphs, etc. Using a common DSL allows someone to make deeply scalable tests. A simple change to the DSL could generate dozens of tests providing coverage through many layers of the test pyramid or even multiple applications.

Cristal-ise is a description-driven software platform originally developed to track the construction of the CMS ECAL detector of the LHC at CERN. This is its core library, known as the kernel, which manages business objects called Items. Items are entirely configured from data, called descriptions, held in other Items. Every change of a state in an Item is a consequence of an execution of an activity in that Item's lifecycle, meaning that Cristal-ise applications are completely traceable, even in their design. It also supports extensive versioning of Item description data, giving the system a high level of flexibility.

Cristal-ise is a description-driven software platform originally developed to track the construction of the CMS ECAL detector of the LHC at CERN. This is its core library, known as the kernel, which manages business objects called Items. Items are entirely configured from data, called descriptions, held in other Items. Every change of a state in an Item is a consequence of an execution of an activity in that Item's lifecycle, meaning that Cristal-ise applications are completely traceable, even in their design. It also supports extensive versioning of Item description data, giving the system a high level of flexibility.

TimoCloud is a Minecraft server/proxy management system ("Cloud System"). It will care about keeping online enough servers/proxies of every kind. But it's more than that. Thank to its algorithms, you'll never have to care again about servers or resources. TimoCloud automatically chooses servers with low CPU usage and enough available RAM to start your instances. And its integrated Flow-System makes updating templates easier than ever before: Edit one file in a server template, and the update will automatically be deployed to all bases (a.k.a. "Wrapper"). But of course, only the changed files will get updated.

This Lutra submodule provides a common framework that other submodules in Lutra use and extend. It includes an implementation of OTTR's data model with classes for templates, instances, types, etc.; a system for handling results and error messages; core interfaces and abstract classes for streamed pipelines for parsing and writing templates and instances; as well as implementation of the TemplateStore, a container for templates, with algorithms for checking correctness of templates and expanding and checking correctness of instances. Lutra is the reference implementation of the OTTR framework. For more information about OTTR, see http://ottr.xyz.

The Limbus System is a small light-weight CDI framework managing the Limbus Core Components. The object graph is represented by an XML configuration file or can be build using the Limbus System API. This module delivers an optional system component that visualizes the object graph and its dependencies after initializing: com.remondis.limbus.system.visualize.LimbusSystemVisualizer This component can be added to the Limbus System. To keep the dependencies of this module transparent and light-weight, the graph renderer is declared as an optional dependency. Add the following dependencies to your project to use the visualisation component: <!-- Graph Stream for Visualization feature This is an optional dependency and only required if using the com.remondis.limbus.system.visualize.LimbusSystemVisualizer --> <dependency> <groupId>org.graphstream</groupId> <artifactId>gs-core</artifactId> <version>1.3</version> </dependency> <dependency> <groupId>org.graphstream</groupId> <artifactId>gs-ui</artifactId> <version>1.3</version> </dependency>

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