Download JAR files tagged by utility with all dependencies

This library contains native facade implementations of the JBrew utility libraries with the Java Native Interface (JNI). This set of libraries features specific optimizations for Unix-based systems in terms of performance and memory. This is achieved through careful tuning using the C programming language to not only control for garbage collection, but also to ensure maximum performance for elected library features. This library in particular features example usages of the JNI in order to test hardware for usability.

This library contains native facade implementations of the JBrew utility libraries with the Java Native Interface (JNI). This set of libraries features specific optimizations for Unix-based systems in terms of performance and memory. This is achieved through careful tuning using the C programming language to not only control for garbage collection, but also to ensure maximum performance for elected library features. This library in particular features example usages of the JNI in order to test hardware for usability.

This library contains native facade implementations of the JBrew utility libraries with the Java Native Interface (JNI). This set of libraries features specific optimizations for Unix-based systems in terms of performance and memory. This is achieved through careful tuning using the C programming language to not only control for garbage collection, but also to ensure maximum performance for elected library features. This library in particular features example usages of the JNI in order to test hardware for usability.

This module provides access to the set of utility classes required to interact with an instance of an AppWorks Gateway from an AppWorks Service. It covers AppWorks dedicated service deployment API, which is a limited subset of the full AppWorks admin API. We currently provide the facility for services to listen to service life-cycle events such as 'service installed', 'service upgraded' and 'service uninstalled'. We also provide the facility for centralised configuration setting management. As AppWorks services are edited from the AppWork Gateway administration console, we provide the ability to respond to updates made here, and also expose creation and update end points for these settings.

<p> MMBase Utils is a part of MMBase, but can also be used in other projects. It contains several kind of utility classes.</p> <p>Highlights:</p> <ul> <li>An implementation of 'events'. Threads can use this to communicate certain things. Using mmbase-clustering, these events can also be sent to other servers.</li> <li>A logging framework</li> <li>A framework for string and byte array transformeration, plus a whole lot of implemetentations for that.</li> <li>Several java.util like classes (collections, dateparsing)</li> <li>File type recognition ('magicfile')</li> <li>The MMBase resourceloader, a generic fall-back mechanism for configuration files and similar resources.</li> <li>...</li> </ul>

This project contains artifacts that provide utility functions for Cloud Bigtable client readers and writers in Google Cloud Dataflow. Dataflow includes a different version of the cloud bigtable client, resulting in a need to have a separation of concerns and an abstraction. More importantly, there is a need for shading and renaming of packages so that Dataflow nad bigtable-hbase-dataflow's two sets of shading (needed for a variety of reasons) don't clash with each other. This submodule does package renaming which is needed for bigtable-hbase-dataflow and alleviates some issues related to developing that module.

Nybatis Data Mapper Framework 1. Logging based on logback but further simple 2. Configuration 3. Message 4. Database It can substitute iBasit or MyBatis. It is very simple but powerful to use 5. Util It provides following utility class - FileUtil - StringUtil - ClassUtil - Reflector - Validator - StopWatcher - ExcelFileUtil this module will run when including following optinal dependency <dependency> <groupId>org.apache.poi</groupId> <artifactId>poi-ooxml</artifactId> <version>3.11</version> </dependency> OR <dependency> <groupId>net.sourceforge.jexcelapi</groupId> <artifactId>jxl</artifactId> <version>2.6.12</version> </dependency>