Download JAR files tagged by expects with all dependencies

This provides dependencies the final WAR artifact requires. The artifact is opinionated about the version ranges it is using. It expects to use Bathe.

Leveraging the JCoRe XML Reader, this project employs a Medline-enabled mapping file to map Medline XML documents to CAS instances. The input is a directory of single XML files, each containing exactly one XML MedlineCitation. The XML format is the one used by NCBI when downloading Medline documents in large batches from the NCBI FTP server. However, the component currently expects single documents instead of whole MedlineCitationSets containing sets of MedlineCitations.

This project produces the Mojo that can build a proper release.xml for the SQuirreLSQL update site, given a directory where the updated jar artifacts are located. This plugin accepts a directory in it's configuration and expects to find three sub-directories there : core, plugins and i18n. It then categorizes the artifacts found in those directories accordingly in the final release.xml file, that is generated in the specified folder.

JCQL is a tool allowing to generate boilerplate java code from existing cassandra schema. It is intended to be used with Cassandra 2.1+ due to support of UDTs (User Defined Types)/Tuples/Collections. Cassandra's UDTs/Tuples/Collections and an ability to introspect schema through java driver make it possible to automatically generate POJOs and corresponding mappers between database and java models. Properly generated java code saves development efforts and is less error-prone compared to hand coding. Accompanied with proper CI and deployment it can also guarantee consistency between database and java models at any point of application lifecycle from development to production rollout. JCQL does not rely on java reflection or annotations which means all discrepancies between actual cassandra schema and what client code expects it to be will be identified during compilation not at runtime in the middle of the night right after production release. No need to worry about Cassandra client code performance implications due to use of reflection.