Download JAR files tagged by case with all dependencies

Allure Test Framework Core is responsible for: * Test report with logs and/or screenshots * Test groups/tags * Data Driven (inside test case, external file) * Test case parallel execution * BDD - Gherkin – Cucumber approach * Run on independent OperatingSystem * Externalize test environment (DEV, QA, PROD) * Adding analytics source code * Update Observers Based on Junit4.12

This artifact contains several miscellaneous, well-known algorithms, which however are rather specific in their concrete use case and therefore not fit for the AutomataLib Utilities library. Examples include Dijkstra's algorithm for the SSSP problem, the Floyd-Warshall algorithm for the APSP problem and Tarjan's algorithm for finding all strongly-connected components in a graph.

Automatic Groovy parameter checker. How to use: 1. Annotate your Groovy classes with @ParamsNotNullNotEmpty; 2. At compile time, code will be added into each of your methods to check each parameter to make sure it is not null and in the case of Collections, Maps and Strings, it is not empty; 3. At run time, if a parameter is null or empty, it will throw an IllegalArgumentException with details about the null or empty parameter. To disable the annotation at compile time, set the ParamsNotNullNotEmpty.NoOpMode flag to true.

This will eventually be a port of Google's libphonenumber to Scala. For now, because I need this functionality quick, it simply wraps libphonenumber. It is NOT complete by any means. I've only added the functionality that I needed. Currently you get a PhoneNumber case class that assumes the country is USA when you don't pass the country in. While you can pass the country in, the only country defined is USA. If you're interested in more from this library, report an issue or send me a pull request. I want to complete it and slowly remove the dependency on Google's libphonenumber

OSGi bundle that contains the JDBC API coming from OpenJDK 1.7. In case of OSGi, it is better to exclude javax.sql.*, com.sun.rowset.* and javax.transaction.* packages from the boot classpath and use them from bundles. Very often javax.transaction.* packages are used from a custom bundle. As javax.sql.XADataSource wires to that package, it is logical to have that in a custom bundle as well so there will be no package wiring issues.

OpenCms-Module 'org.opencms.workplace.handler'. <p>This module contains the OpenCms Workplace handler files.</p> <p>It includes the 404 and 500 error handlers that are showed in case of an error of a frontend application.</p> <p><i>&copy; 2013 by Alkacon Software GmbH (http://www.alkacon.com).</i></p> OpenCms is a Content Management System that is based on Open Source Software. Complex Intranet and Internet websites can be quickly and cost-effectively created, maintained and managed.

This nifi-utils module should be a general purpose place to store widely and generally useful functions that any component might want to leverage. NO DEPENDENCIES should be added. This module is likely to be leveraged by every extension and should not bring along any other dependencies. The only dependency intended is the nifi-api and even this is expected to be already provided in any case where it would be used. The typical place this util would be found is within a nar and all nars already have nifi-api as a parent dependency. The nifi-api can be thought of as a NiFi Application Container level dependency.

Geordi Test Framework is a Kotlin-based testing framework integrating with JUnit 5's TestTemplate for dynamic and parameterized testing. It supports file-based and parameter-based scenarios, suitable for various testing contexts. Key features include dynamic test case generation, SimulationGroup for scenario organization, and integration with JUnit 5's advanced features. It also includes a utility class, UnitSim, for method-level testing and mocking with Mockk. Geordi is inspired by the Spock framework, aiming to provide comparable functionality in a Kotlin-optimized package.

MulTEx is a simple, but powerful framework for organizing exceptions and messages in a multi-tier Java software system. It offers the key features: Causal chains/trees as a means to capture low-level error information. Redundancy-free stack traces and message chains in the case of indirectly caused exceptions. Internationalized message texts and parameters for exceptions. Services for reporting an exception chain/tree onto streams and dialogs. A standard way for writing method bodies with regard to exceptions. A collection of utilities for centralized exception reporting.

A very simple, no-dependencies drawing API providing some primitive operations including lines, rectangles, circles, ellipses, arcs. It doesn't actually draw TO anything, you must provide your own implementation of Backing to actually paint the pixels. This project is intended for use with Snake, my project for Razer devices on Linux, but is made available in case others may find it useful. It doesn't have anything fancy like anti-alias, transformations or even line widths, contributions welcome though!