Download JAR files tagged by works with all dependencies

Ferris SLiSE (Spectral Line Search Engine) Common contains code which is common to the different ways SLiSE is packaged and distributed. Because of the way Maven works, it's easier to create seperate projects to package and distribute SLiSE as either an Applet Application, a Desktop Application, or a Java Web Start Application mvn clean site package 0.0.1 Convert from Oak to Ferris

Spring Batch archetypes are simple project templates containing just enough code to get you started running a job. For more detailed examples of using particular features of the framework, look at the Spring Batch Samples project. Currently the archetypes are deployed as regular Maven projects (not archetypes), because of limitations in the archetype plugin (or our understanding of how it works). For most effective use, copy one into Eclipse and use Q4E to manage the dependencies.

This small library provides an optimized solution to a problem where tasks for a particular key need to be processed sequentially as they arrive. This kind of problem can be solved by a SingleThreadExecutor, however it is not efficient. The issue is that the tasks for unrelated keys are not being processed in parallel, instead they are put into a queue common to all keys and wait for the single thread to execute them. This library allows them to be executed concurrently. Moreover this library works well in a situation where all the possible keys and their number is not known upfront.

JARTs are Java-based Asynchronous Real Time sockets. JART uses JNA to build a pure Java TCP/IP stack upon Netmap. It is implemented in imperative style (no TCP state machine) using asynchronous programming with the help of ea-async. JART runs on both Linux (with the proper Netmap kernel module) and FreeBSD with Netmap enabled. FreeBSD 12.1+ has Netmap in the kernel by default so it works "out of the box". While JART has proven fairly robust in limited testing, it is still a work-in-progress and may not be suitable for production use. Pull requests welcome!

The RestFixture is a FitNesse (http://fitnesse.org) fixture that allows developers and/or product owners to write test fixtures for REST services with simplicity in mind. The idea is to write tests that are self documenting and easy to write and read, without the need to write Java code. The fixture allows test writers to express tests as actions (any of the allowed HTTP methods) to operate on resource URIs and express expectations on the content of the return code, headers and body. All without writing one single line of Java code. And it also works as a living/executable documentation of the API.

OpenCL4Java is a thin Java wrapper around OpenCL's C API. It uses JNA as its interop layer library, which means it works on all of the (many) JNA-supported platforms (see http://jna.dev.java.net/). It is autogenerated by JNAerator (http://jnaerator.googlecode.com/), so updates to newer OpenCL specs are a matter of seconds. Note that OpenCL4Java is used by JavaCL, an Object-Oriented API that presents OpenCL in a much more practical, powerful and idiomatic way to Java. For more info, please visit http://code.google.com/p/nativelibs4java/wiki/OpenCL.

An low latency, lock free, primitive bounded blocking queue backed by an int[]. This class mimics the interface of {@linkplain java.util.concurrent.BlockingQueue BlockingQueue}, however works with primitive ints rather than objects, so is unable to actually implement the BlockingQueue. This class takes advantage of the Unsafe.putOrderedObject, which allows us to create non-blocking code with guaranteed writes. These writes will not be re-orderd by instruction reordering. Under the covers it uses the faster store-store barrier, rather than the the slower store-load barrier, which is used when doing a volatile write. One of the trade off with this improved performance is we are limited to a single producer, single consumer.