Download JAR files tagged by under with all dependencies

This project allows a user to interact with ESP services in a controlled manner. The API calls available under org.hpccsystems.ws.client.platform allow for a user to target ESP's across multiple environments running a range of hpccsystems-platform versions. There is no guarantee that if a user utilizes org.hpccsystems.ws.client.gen generated stub code from wsdl, that the calls will be backwards compatible with older hpccsystems-platform versions.

A bundle project producing JAX-RS RI bundles. The primary artifact is an "all-in-one" OSGi-fied JAX-RS RI bundle (jaxrs-ri.jar). Attached to that are two compressed JAX-RS RI archives. The first archive (jaxrs-ri.zip) consists of binary RI bits and contains the API jar (under "api" directory), RI libraries (under "lib" directory) as well as all external RI dependencies (under "ext" directory). The secondary archive (jaxrs-ri-src.zip) contains buildable JAX-RS RI source bundle and contains the API jar (under "api" directory), RI sources (under "src" directory) as well as all external RI dependencies (under "ext" directory). The second archive also contains "build.xml" ANT script that builds the RI sources. To build the JAX-RS RI simply unzip the archive, cd to the created jaxrs-ri directory and invoke "ant" from the command line.

jBiDiB jbidibc USB POM Install the libusb drivers for using the libusb access. Under Windows OS you must install the Zadig driver as described here: https://github.com/libusb/libusb/wiki/Windows. Zadic can be downloaded from: http://zadig.akeo.ie/ In the Zadig UI you must check Options > List all devices and the select the 'USB-EPP /I2C... CH341A' device. Then select the target driver with the spinners (I used libusb-win32 (v1.2.6.0)) and click the 'Install driver' button.

Library for programmatic AsciiDoc generation. The AsciiDoc name is trademarked by the Eclipse Foundation (https://www.eclipse.org/). This project is *not* part of the specification effort for _AsciiDoc_ under the AsciiDoc Working Group. See https://projects.eclipse.org/proposals/asciidoc-language and https://accounts.eclipse.org/mailing-list/asciidoc-wg. However, we are happy to help with transfer of source code, if any project (under the umbrella of the AsciiDoc Working Group) is willing to take over.

jBiDiB jbidibc CH341A POM Install the libusb drivers for using the libusb access. Under Windows OS you must install the Zadig driver as described here: https://github.com/libusb/libusb/wiki/Windows. Zadic can be downloaded from: http://zadig.akeo.ie/ In the Zadig UI you must check Options > List all devices and the select the 'USB-EPP /I2C... CH341A' device. Then select the target driver with the spinners (I used libusb-win32 (v1.2.6.0)) and click the 'Install driver' button.

Stevia is a QA Framework unifying the Selenium-RC and Webdriver APIs under a common uniform API that handles all differences. Using Stevia allows the QA Engineer to seamlessly switch between Selenium-RC and Webdriver, enhance by adding custom webdrivers and other artifacts. By design both drivers play under Selenium Grid and support extended reporting functionality via ReportNG, including remote screenshots.

The Google Closure Library is a collection of JavaScript code designed for use with the Google Closure JavaScript Compiler. This non-official distribution was prepared by the ClojureScript team at http://clojure.org/ This package contains extensions to the Google Closure Library using third-party components, which may be distributed under licenses other than the Apache license. Licenses for individual library components may be found in source-code comments.

Butor Framework is a stack that enables fast and easy creation of HTTP services (asynchronous and synchronous). It consists of several modules for different layers, such as data access, services, Webapps, JSON serialization and test utilities. It sits on top of popular and proven libraries such as Google Guava, Spring, Bootstrap. The project is released under APL 2.0. This project is a pom module, the parent for other modules of the framework.

javaFMI is a Java Library for the functional mock-up interface (or FMI). FMI defines a standardized interface to be used in computer simulations. The FMI Standard has beed developed by a large number of software companies and research centers that have worked in a cooperation project under the name of MODELISAR. This library addresses the connection of a java application with a FMU (functional mock-up unit).