Download JAR files tagged by first with all dependencies

The aim of the SAT4J library is to provide an efficient library of SAT solvers in Java. Compared to the OpenSAT project, the SAT4J library targets first users of SAT "black boxes", willing to embed SAT technologies into their application without worrying about the details. Since we use the library for our own research, it is also possible for SAT researchers to use it as a basis for their work.

JExample is an extensions of JUnit that improves defect localizaton by changing the way you structure your tests. It introduces first-class dependencies. If test B depends on A, the return value of A can be used as B's fixture. And if A test fails, B and all other dependees of A are skipped and marked as white. We show in an empirical study that JExample improves performance and defect localization.

The RepeatCheckUntilVerified Utility offers a robust asynchronous mechanism for performing repeated condition checks with configurable retries, initial delays, and optional backup actions. Designed for Kotlin-based applications, it simplifies the implementation of retry logic for operations that require validation through repeated attempts, such as network requests, file I/O operations, or any condition-dependent tasks. With features like adjustable timing, maximum attempt control, and failure management through backup actions, it ensures resilience and flexibility in handling operations that may not succeed on the first try. Ideal for applications requiring high reliability and precise control over task verification processes.

Wicket is a Java web application framework that takes simplicity, separation of concerns and ease of development to a whole new level. Wicket pages can be mocked up, previewed and later revised using standard WYSIWYG HTML design tools. Dynamic content processing and form handling is all handled in Java code using a first-class component model backed by POJO data beans that can easily be persisted using your favorite technology.

The goal of this project is to connect architecture documentation and models while identifying missing or deviating elements (inconsistencies). An element can be any representable item of the model, like a component or a relation. To do so, we first create trace links and then make use of them and other information to identify inconsistencies. ArDoCo is actively developed by researchers of the Modelling for Continuous Software Engineering (MCSE) group of KASTEL - Institute of Information Security and Dependability at the KIT.

The project provides Result-type similar to Result-type in Rust that allows to return either successfull result or otherwise some kind of error. In Java native way of reporting errors are exceptions, either checked or unchecked, but Result-type provides a way to pass error enformation as a first-class value through the code written in functional style. Routines are provided for interoperability of normal code that uses exception and functional code that uses Result-type, so that exceptions can be catched and propagated as errors in Result-type and then rethrown again later in the control-flow.