Download JAR files tagged by like with all dependencies

Our first work is to create a set of tools to help in the adoption drools in our local companies. Those tools are here to make drools "enterprise ready "by adopting an industrial approach : we want to put in common a standard library that we shall all use in our drools project. This tools are of course open source and we use a friendly apache licence. Indeed, drools like any other jboss framework is a swiss knife that offers all possibilities. Our framework implements the best practices that we implemented in real projects that goes from how to monitor, report and supervise the use of drools. We hope you will enjoy our work and invite you to contact us in case of trouble. But do not forget we are a community !

The UnboundID LDAP SDK for Java is a fast, comprehensive, and easy-to-use Java API for communicating with LDAP directory servers and performing related tasks like reading and writing LDIF, encoding and decoding data using base64 and ASN.1 BER, and performing secure communication. This package contains the Minimal Edition of the LDAP SDK, which is a stripped-down version of the Standard Edition that includes full support for the LDAP protocol and LDIF parsing, but omits a number of optional elements, like many of the controls and extended operations, the LDAP persistence framework, and LDAP listener framework. The Minimal Edition is primarily intended for use in space-constrained and/or memory-constrained environments, like in Android apps or embedded systems.

The UnboundID LDAP SDK for Java is a fast, comprehensive, and easy-to-use Java API for communicating with LDAP directory servers and performing related tasks like reading and writing LDIF, encoding and decoding data using base64 and ASN.1 BER, and performing secure communication. This package contains the Commercial Edition of the LDAP SDK, which includes all of the general-purpose functionality contained in the Standard Edition, plus additional functionality specific to UnboundID/Ping Identity server products.

This powerful reporting library aims to simplify producing reports using iText. The most demanding and coding intensive tasks when producing reports with iText are how to get from data to report elements, how to style those blocks and how to evaluate (debug) the resulting report layout. Exactly those three tasks are simplified by this library: xml configuration and/or annotations to transform existing Java data objects into report block, provide styling information (css like, syntax independent) seperate from code, a firebug like debug mode to help evaluate your report.

This powerful reporting library aims to simplify producing reports using iText. The most demanding and coding intensive tasks when producing reports with iText are how to get from data to report elements, how to style those blocks and how to evaluate (debug) the resulting report layout. Exactly those three tasks are simplified by this library: xml configuration and/or annotations to transform existing Java data objects into report block, provide styling information (css like, syntax independent) seperate from code, a firebug like debug mode to help evaluate your report.

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.