Download JAR files tagged by changed with all dependencies

JWAT-Tools uses the available JWAT libraries to make high level tasks available either from command-line or programmatically. Common tasks include: Test, Compress, Decompress, CDX, Arc2Warc. More specialised tasks include: Changed, ContainerMD, Delete, Extract, Interval, PathIndex, Unpack, Headers2CDX.

Project, initially inspired in the open source project JBooleanExpression, located in http://sourceforge.net/projects/jboolexpr/, which is a simple Java API to evaluate a Boolean String Expression like "!true&&false||true" (parse a Boolean String Expression to a boolean primitive type). The build system of this project was changed to Maven and a new operation (XOR) was also included.

Helping synchronization between clients and servers accross a network. The client is expected to have pushed its changes to the server and then requests the library to pull changes from the server. Clients of the library must provide on the server a way to serialize items and an endpoint, as well as a way to deserialize items and to access the server endpoint on the client. The algorithm requires O(log(n)) roundtrips to the server and consumes a total bandwidth of O(n) where n is the number of items which changed on the server since the last synchronization

ExecutorService's type parameters changed between JDK5 and JDK6 in a way that makes it impossible for our invokeAll/invokeAny methods to match both at compile time. This project builds a JDK6-like copy of ExecutorService (but with JDK5 compiler settings to ensure that it will work with JRE5 at runtime). It also builds a version of AbstractExecutorService that is equivalent to a JDK5 version but using the JDK6 type parameters for the invokeAll/invokeAny methods just as with ExecutorService. This project's is then used in the bootstrap class path of Guava proper.

ExecutorService's type parameters changed between JDK5 and JDK6 in a way that makes it impossible for our invokeAll/invokeAny methods to match both at compile time. This project builds a JDK6-like copy of ExecutorService (but with JDK5 compiler settings to ensure that it will work with JRE5 at runtime). This project's is then used in the bootstrap class path of Guava proper.

ExecutorService's type parameters changed between JDK5 and JDK6 in a way that makes it impossible for our invokeAll/invokeAny methods to match both at compile time. This project builds a JDK6-like copy of ExecutorService (but with JDK5 compiler settings to ensure that it will work with JRE5 at runtime). This project's is then used in the bootstrap class path of Guava proper.

An SLF4J log provider that directly implements the SLF4J API and provides logging output suitable for console output (i.e. not to a file). The width of the output is restricted to the terminal width, with the possibility to split the width into multiple sections, each which may be a fixed width, or 'auto' which divides all remaining space amongst other automative sections. Any log attribute fields may then be placed in any of the sections with a particular alignment. Text will not overflow out of its section. Sections may be colour or styled with other text attributes, including hyperlinks for supported termins. Emoticons and other graphical sequences may be used in place of log levels. Configuration is achieved via 'ini' type files, which are reload automatically when changed.