Download JAR files tagged by writers with all dependencies

This project contains artifacts that provide Cloud Bigtable client readers and writers in Google Cloud Dataflow.

This Lutra submodule implements readers and writers for the stOTTR formalisation format (https://spec.ottr.xyz/stOTTR/). stOTTR is a custom-built serialisation format for OTTR intended to be easy to read and write for humans (and computers!). Lutra is the reference implementation of the OTTR framework. For more information about OTTR, see http://ottr.xyz.

This Lutra submodule implements readers and writers for the wOTTR serialisation format (https://spec.ottr.xyz/wOTTR/0.4/). wOTTR is a syntax for writing templates and instances in RDF intended for publishing templates and instances on the web or for storage in a triplestore. Lutra is the reference implementation of the OTTR framework. For more information about OTTR, see http://ottr.xyz.

Power Libraries is a small project to collect some repeatedly needed or otherwise useful Java 8 classes in a collection of tiny libraries. IO Power is the first and really tiny library of the Power Libraries. It contains some simple helper method for opening Input- and Outputstreams. The main purpose of IO Power is to make opening streams, readers and writers less cluttered and simple to understand.

This module groups all different output writers. Different output writers have different dependencies. To ensure that those dependencies do not leak to other output writer, or that we can limit to number of dependencies at runtime, output writers are split into separate modules based on the dependencies they use. For example, the CloudWatch output writers depends on the AWS SDK, which is quite large and not used by any other output writer. If you only want to send metrics to Graphite, there should be no need to have the AWS SDK in your classpath at runtime. Some dependencies are also problematic. They can introduce incompatibilities. For example, a few writers are based directly on log4j or logback. This direct dependence breaks the use of SLF4J. By isolating those output writers to a specific module, we can ensure this has minimal impact.

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.

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.