Download JAR files tagged by implementation with all dependencies

This project contains a Java implementation of median relational generalized learning vector quantization as proposed by Nebel, Hammer, Frohberg, and Villmann (2015, doi:10.1016/j.neucom.2014.12.096). Given a matrix of pairwise distances D and a vector of labels Y it identifies prototypical data points (i.e. rows of D) which help to classify the data set using a simple nearest neighbor rule. In particular, the algorithm optimizes the generalized learning vector quantization cost function (Sato and Yamada, 1995) via an expectation maximization scheme where in each iteration one prototype 'jumps' to another data point in order to improve the cost function. If the cost function can not be improved anymore for any of the data points, the algorithm terminates.

ISO 13616-1:2007 specifies the elements of an international bank account number (IBAN) used to facilitate the processing of data internationally in data interchange, in financial environments as well as within and between other industries. The IBAN is designed for automated processing, but can also be used conveniently in other media interchange when appropriate (e.g. paper document exchange, etc.). ISO 13616-1:2007 does not specify internal procedures, file organization techniques, storage media, languages, etc. to be used in its implementation, nor is it designed to facilitate the routing of messages within a network. It is applicable to the textual data which might be conveyed through a system (network). This project provides a general purpose ISO 13616-1:2007 compatible IBAN Java class.

This module contains library classes for accessing the ThreadFix REST API. The ThreadFix IDE plugins use this library to retrieve application and vulnerability marker information, and in the ThreadFix scanner plugins to get endpoint information and upload scans to ThreadFix applications. The easiest way to start using the library is with the PluginClient or ThreadFixRestClient classes. Both have constructors that take a PropertiesManager instance, which holds the ThreadFix API key and url information. The default PropertiesManager implementation stores these properties in threadfix.properties, but the ThreadFix plugins extend the default PropertiesManager class to override this behavior for the target platform.

Tinder is a Java based XMPP library, providing an implementation for XMPP stanzas and components. Tinders origins lie in code that's shared between Jive Software's Openfire and Whack implementations. The implementation that's provided in Tinder hasn't been written again from scratch. Instead, code has been moved from the original projects into Tinder, preserving al of the existing features and functionality. Most of the code that's now in Tinder is based on the org.xmpp package implementation that previously existed in Openfire and Whack. This is the code that defines classes such as Packet, JID, IQ, Component and their extensions. Additionally, some multi-purpose code (such as the DataForm and Result Set Management implementations have been moved to Tinder as well.

The Java JDK includes various means of creating/consuming compressed files. What is missing is easy way of creating lazy streamed zip archive, in spirit of java.util.zip.DeflaterInputStream. This implementation relies on the fact that the PKZIP specification allows archiving data streams of sizes not known upfront. This implies that the archives produced will be readable only by tools aware of this trick. Notably, java.util.zip.ZipInputStream is OK with that, so we use it to test compatibility.

Oxalis integration test. Compiles and packages everything, after which the web container is started in the pre-integration-test phase, the .war file is deployed and the tests are executed in the integration-test phase. After the tests have been executed, the web container is stopped in the post-integration-test phase. The reason for using failsafe is the fact that Surefire would fail the build in the integration-test phase, without taking down the server in the post-integration-test phase. This implementation uses Tomcat, but you may change this to your liking. See http://cargo.codehaus.org/Maven2+plugin for more information.

The crypto4j library provides a simple and pluggable crypto abstraction library for Java, including both cryptographic primitives and the artifacts defined in the JOSE standard. This library separates the cryptographic primitives from the JOSE artifacts. The library uses the algorithms available through JCA (JCE). The implementations of the cryptographic primitives provided in this library rely on the standard JCA implementation, and can be configured and extended through the JCA mechanisms. The JOSE portion of the library allows custom extensions by either replacing the provided JOSE artifact implementations with custom implementations, or by adding new JOSE artifacts, for instance in form of additional algorithms, which is particularly useful in case that the JOSE standard is updated or in case custom extensions to the JOSE standard should be implemented. The implementations available in this library generally come in two variants: a standard implementation of the primitives and advanced algorithms, and a high-performance implementation that takes advantage of implementation patterns that do not compromise cryprographic security, but speed up the overall processing time.

Alpheus AFP Parser is a library and parser for the IBM Advanced Function Presentation (AFP) document/print stream format. Alpheus covers all AFP specifications: MO:DCA, BCOCA, CMOCA, FOCA, GOCA, IOCA, and PTOCA. It is a complete implementation. Every Structured Field, Repeating Group, and Triplet is fully implemented as Java class. Alpheus AFP Parser was written from scratch and has no external dependencies. Copyright 2015,2016 Rudolf Fiala Alpheus AFP Parser is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

Nuun Kernel is a software kernel for framework creation. It brings a powerful plugin design plus a JSR 330 compliant injection mechanism backed by Guice. Plugin benefits from kernel capabilities by sendings request to it : - kernel params request : - Classpath scans request :on class by name, annotation, meta annotation or more generally Predicate - Binding Request : Nuun Kernel provides an SPI in order to bring IOC from other vendors. Nuun Kernel come with 2 plugins: - Configuration Plugin : a plugin that inject the good property based on @Property annotation. - Log plugin : a Log handler that inject the good Log implementation

Welcome to the Blazegraph/TinkerPop3 project. The TP3 implementation has some significant differences from the TP2 version. The data model has been changed to use RDF*, an RDF reification framework described here: https://wiki.blazegraph.com/wiki/index.php/Reification_Done_Right. The concept behind blazegraph-gremlin is that property graph (PG) data can be loaded and accessed via the TinkerPop3 API, but underneath the hood the data will be stored as RDF using the PG data model described in this document. Once PG data has been loaded you can interact with it just like you would interact with ordinary RDF - you can run SPARQL queries or interact with the data via the SAIL API. It just works. The PG data model is also customizable via a round-tripping interface called the BlazeValueFactory, also described in detail in this document.