Download JAR files tagged by also with all dependencies

The chart-fx charting library is an extension in the spirit of Oracle's XYChart and performance/time-proven JDataViewer charting functionalities. Emphasis was put on plotting performance for both large number of data points and real-time displays, as well as scientific accuracies leading to error bar/surface plots, and other scientific plotting features (parameter measurements, fitting, multiple axes, zoom, ...). The library also contains a small set of math routines that can operate directly on the DataSet primitive for fitting, computing spectra, linear algebra, FIR/IIR filtering, and other functionalities common to signal processing.

Concourse is a distributed database warehouse for transactions, search, and analytics across time. Developers use Concourse to quickly build mission critical software while also benefiting from real time insight into their most important data. With Concourse, end-to-end data management requires no extra infrastructure, no prior configuration and no additional coding–all of which greatly reduce costs and allow developers to focus on core business problems.

1) This module contains various Zookeeper recipe implementations. 2) The recipe directory name should specify the name of the recipe you are implementing - eg. zookeeper-recipes-lock. 3) It would be great if you can provide both the java and c recipes for the zookeeper recipes. C recipes go in to zookeeper-recipes/zookeeper-recipes-[recipe-name]/src/c Java implementation goes into zookeeper-recipes/zookeeper-recipes-[recipe-name]/src/java. 4) The recipes hold high standards like our zookeeper c/java libraries, so make sure that you include some unit testing with both the c and java recipe code. 5) Also, please name your c client public methods as zkr_recipe-name_methodname (eg. zkr_lock_lock in zookeeper-recipes-lock/src/c) 6) To run the c tests in all the recipes, - make sure the main zookeeper c libraries in zookeeper-client-c are compiled. Run autoreconf -if;./configure; make. The libraries will be installed in {top}/src/c/.libs. - run autoreconf if;./configure;make run-check in zookeeper-recipes/$recipename/src/c

This library is the the backend for the Fitzhì solution. Fitzhì aims to gather all technical data regarding your application portfolio into ONE single portal. Fitzhì provides also analysis and assessments at the project scope, but its main target is the portfolio. The main ambition is to provide a global, and dynamic vision of the technical risk for your IT. The dream functionality for Fitzhì should be the ONE single dashboard, one Single Point Point Of Quality, available for the CTO, or CIO, and ready to resume in one second, one view, the current situation and the historic trend.

The Zello Channels SDK allows you to integrate Zello push-to-talk into your own application. The SDK communicates with a Zello server over a web socket connection using a JSON-based protocol, and offers a simple API to send and receive audio, images, and text over Zello channels. Supported features include: Send voice messages from the device microphone Play incoming voice messages through the device speaker Send voice messages from your own audio code, e.g. from a file Receive voice message data with your own audio code with optional pass-through to the device speaker Send and recieve text messages Send and receive images Send the device's current location, and receive location messages from other users The protocol specification is also available if you prefer to develop your own client in-house.

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.