Download JAR files tagged by submodules with all dependencies

This is the main aggregator for all jre submodules. It will contain all of the default implementations for all java runtimes, and leave extension points for any cross-platform differences between restricted platforms, like android, appengine or servlet environments.

A code example for how to use the soapworks library. The submodules are: server: a sample server app that runs a web service. clientlib: the matching web service client library that uses soap/wsdl to connect to the server. clientapp: a sample client app that uses the clientlib to connect to the server. To test it, run the Boot class and then execute the PingServiceImplTest.

We skip staging of some submodules, but if you skip staging in the last submodule it skips all staging (a serious error in the design of the nexus staging plugin that has been closed "wontfix" - issues.sonatype.org/browse/NEXUS-9138). The backup solution to that problem is to skip the deploy phase in the submodule. We want to deploy the artifact of bedrock-site to AWS, but not publish the war file to nexus. The recommended solution is to add this dummy node at the end of the submodule list.

The Multi Schema Validation toolkit is a Java based toolkit consisting of 8 different submodules. The core module is the Multi-Schema XML Validator (MSV) for the validation of XML documents against several kinds of XML schemata The core supports RELAX NG, RELAX Namespace, RELAX Core, TREX, XML DTDs, and a subset of XML Schema Part 1. This core offers an API useable for programmatic access of the grammar, such as code generation.

This plugin is designed to be used in artifacts that generate docker images. babysaur will create a manifest file in artifacts that create docker images and you should use mamasaur in the reactor that controls them. It depends on the "modules" section and will walk down through your POM files looking for submodules of submodules. Given this does not work with Maven when building differences, you should generally NOT use multiple levels of submodules with maven reactors.

This is a client to access Cloud Bigtable (https://cloud.google.com/bigtable/) via the HBase APIs. There are a handful of modules in this project. The bigtable-hbase-x.x projects are intendned to be the projects which users interact with. The x.x versions in the bigtable-hbase-x.x projects represent the hbase major and minor versions which the project supports. For example, bigtable-hbase-1.0 will integrate with all hbase 1.0.x releases and bigtable-hbase-1.1 will integrate with all hbase 1.1.* releases. The bigtable-protos, bigtable-client-core and bigtable-hbase modules are meant to be used as components of bigtable-hbase-x.x. Those submodules may be usedful outside of the bigtable-hbase-x.x projects, but have not been thoroughly tested in other scenarios.

This Lutra submodule provides a common framework that other submodules in Lutra use and extend. It includes an implementation of OTTR's data model with classes for templates, instances, types, etc.; a system for handling results and error messages; core interfaces and abstract classes for streamed pipelines for parsing and writing templates and instances; as well as implementation of the TemplateStore, a container for templates, with algorithms for checking correctness of templates and expanding and checking correctness of instances. Lutra is the reference implementation of the OTTR framework. For more information about OTTR, see http://ottr.xyz.