Download JAR files tagged by util with all dependencies

The purpose of reb4j is to provide a pure Java wrapper around the regular expression syntax provided by the JRE's java.util.regex.Pattern class in order to facilitate programmatic construction of regular expressions while taking advantage of compile-time syntax checking. This sub-project contains the Scala implementation of reb4j.

The purpose of reb4j is to provide a pure Java wrapper around the regular expression syntax provided by the JRE's java.util.regex.Pattern class in order to facilitate programmatic construction of regular expressions while taking advantage of compile-time syntax checking. This sub-project contains the Java implementation of reb4j.

mime-util is a simple to use, small, light weight and fast open source java utility library that can detect the mime types of files and streams. Due to the use of regular expressions and the java.nio packages it requires at least Java 1.4. mime-util uses file extension mappings and the magic.mime rules files located on your system as used by the Unix file(1) command. For OS's that do not support the Unix file(1) command, such as Windows, the library comes pre-packaged with a generic magic.mime file.

This nifi-utils module should be a general purpose place to store widely and generally useful functions that any component might want to leverage. NO DEPENDENCIES should be added. This module is likely to be leveraged by every extension and should not bring along any other dependencies. The only dependency intended is the nifi-api and even this is expected to be already provided in any case where it would be used. The typical place this util would be found is within a nar and all nars already have nifi-api as a parent dependency. The nifi-api can be thought of as a NiFi Application Container level dependency.

Easy to install library for adding dynamic display, control and configuration of java.util.logging to any swing based application. Useful for debugging apps in production situations; can interactively configure logging while an application is running including adding a handler to save logging output to a file. Changes made to an application's default/startup logging can be saved and automatically applied at startup. LogMan "single" library package for use in swing apps. The jar can be executed, "java -jar xxx", for a demo of the library. See com.raelity.logman.demo.Main for an example of adding the library to a swing app.

<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>

An empty artifact that Guava depends on to signal that it is providing ListenableFuture -- but is also available in a second "version" that contains com.google.common.util.concurrent.ListenableFuture class, without any other Guava classes. The idea is: - If users want only ListenableFuture, they depend on listenablefuture-1.0. - If users want all of Guava, they depend on guava, which, as of Guava 27.0, depends on listenablefuture-9999.0-empty-to-avoid-conflict-with-guava. The 9999.0-... version number is enough for some build systems (notably, Gradle) to select that empty artifact over the "real" listenablefuture-1.0 -- avoiding a conflict with the copy of ListenableFuture in guava itself. If users are using an older version of Guava or a build system other than Gradle, they may see class conflicts. If so, they can solve them by manually excluding the listenablefuture artifact or manually forcing their build systems to use 9999.0-....

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.

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>

A timer using the crontab syntax and additional binary input to provide a resolution of one second (1000 ms / 1000 millis / 1s). The timer uses the whiteboard pattern to notify the clients. There are only a few dependencies to commons-codec, osgi and osgi-blueprint. The bundle 'org.i3xx.step/org.i3xx.step.clockmongo' provides a store for the clock configuration based on mongodb. The additional dependency is 'org.mongodb/mongo-java-driver'. The bundle 'org.i3xx.util/org.i3xx.util.whiteboard' can be used to avoid a dependency to bundles used. In other words, your bundle can use the clock but need no dependency to the bundle 'org.i3xx.step.clock'. Take a look at the description there.