Download JAR files tagged by however with all dependencies

HBase module that provides out of process block cache. Currently Memcached is the reference implementation for external block cache. External block caches allow HBase to take advantage of other more complex caches that can live longer than the HBase regionserver process and are not necessarily tied to a single computer life time. However external block caches add in extra operational overhead.

Datastore SQL engine (DSQL) for Google appengine datastore. DSQL extends gae datastore in implementing local joins between datastore kinds as well as providing local filtering for unindexed properties. DSQL uses familiar sql-syntax. SQL joins are optimized using datastore statistics. It is assumed that datastore schema is designed like relational db. However parent/child relationships are supported. Also supported are special datatypes in package com.google.appengine.api.datastore like Email, Phonenumber, ...

This artifact contains several miscellaneous, well-known algorithms, which however are rather specific in their concrete use case and therefore not fit for the AutomataLib Utilities library. Examples include Dijkstra's algorithm for the SSSP problem, the Floyd-Warshall algorithm for the APSP problem and Tarjan's algorithm for finding all strongly-connected components in a graph.

A backport for java.util.function to be used in java versions older than 1.8. As there are no default methods before 1.8 the backport is very limited. It only allows to create libraries with modern APIs to allow 1.8 code to use nice and natural lambdas without locking out users with older java versions. ATTENTION: This only works with -Xbootclasspath. Also it is inofficial and invalid according to JCP/JSR. However, we need a working update-path to 1.8.

This is a set of utilities and classes that I have found useful over the years. In my career spanning over a decade, I have time and again written the same code or some part of the code over and over again. I never found the time to collate the details in a reusable library. This project will be a collection of such files. The work that I have been doing is more than 5 years old, however the project has been conceived in 2011.

This project produces a maven mojo that can set the System property "squirrelsql.version" so that it can be used globally by the installers and the update-site projects. It accepts the project version as an argument which it uses to decide what the squirrelsql.version should be. If the project version ends with "-SNAPSHOT", then the squirrelsql.version will be set to Snapshot-{timestamp} where {timestamp} is the current timestamp in the form of YYYYMMDD_HHMM. If however, the project version does not end with "-SNAPSHOT", then squirrelsql.version will be set to the value of the project version.

When generating XML schema from Java source code using the schemagen tool a common approach is to use the @XmlElementWrapper and @XmlElement annotations to handle schema generation for collections. However, when generating Java source from a schema using the xjc tool the resulting code is not created with these annotations. Instead, the generated Java source contains "injected" inner classes to accommodate the collection of elements contained within an element.

API for stackable stateful encoders and decoders. Such codec interfaces allow for the efficient processing of data as it is made available while maintaining small actively processing footprints. Of course these aspects depend on the implementation as well however this API standardizes the minimum set of interfaces associated with codec's that are stateful. Until this API is added to the commons-codec project several interfaces and classes here are duplicated to minimize the number of dependencies: namely a dependency on commons-codec will be avoided.

The Shell Card Management API is REST-based and employs OAUTH 2.0,Basic and ApiKey authentication. The API endpoints accept JSON-encoded request bodies, return JSON-encoded responses and use standard HTTP response codes. All resources are located in the Shell Card Platform. The Shell Card Platform is the overall platform that encompasses all the internal Shell systems used to manage resources. The internal workings of the platform are not important when interacting with the API. However, it is worth noting that the platform uses a microservice architecture to communicate with various backend systems and some API calls are processed asynchronously. All endpoints use the POST verb for retrieving, updating, creating and deleting resources in the Shell Card Platform. The endpoints that retrieve resources from the Shell Card Platform allow flexible search parameters in the API request body.