Download JAR files tagged by artifacts with all dependencies

This part of the project contains the core api, xml schemas for each supported xmpp protocol and the jaxb generated code. Because this section rarely changes (i.e. when a new protocol is added or when an existing protocol is updated by the XMPP Standards Foundation its usually not required to actually build from this directory but allow maven to retrieve the pre-built artifacts instead. Doing this will save you a lot of time as there are over 100 modules within this part of the project.

Responsible for deploying additional artifacts such as schemas and release distributions to MuleForge. Using this plugin ensures consistency of hosted files. Users should use the Mule Maven archetypes to generate POM.xml files for thier project. These POMs will be configured with the standard MuleForge plugins and will comply to the MuleForge rules for build and deployment.

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 crypto4j library provides a simple and pluggable crypto abstraction library for Java, including both cryptographic primitives and the artifacts defined in the JOSE standard. This library separates the cryptographic primitives from the JOSE artifacts. The library uses the algorithms available through JCA (JCE). The implementations of the cryptographic primitives provided in this library rely on the standard JCA implementation, and can be configured and extended through the JCA mechanisms. The JOSE portion of the library allows custom extensions by either replacing the provided JOSE artifact implementations with custom implementations, or by adding new JOSE artifacts, for instance in form of additional algorithms, which is particularly useful in case that the JOSE standard is updated or in case custom extensions to the JOSE standard should be implemented. The implementations available in this library generally come in two variants: a standard implementation of the primitives and advanced algorithms, and a high-performance implementation that takes advantage of implementation patterns that do not compromise cryprographic security, but speed up the overall processing time.

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.

This plugin gives SQuirreLSQL client the ability to configure alternate LaFs provided by the plugin as well as others that the user can provide. All dependencies listed with a groupId of net.sf.squirrel-sql and artifactId starting with squirrelsql-lf- are externally available open-source look and feels whose project maintainers have decided to not use maven, or those which were built and maintained only before the introduction of maven. Maven's central repository policy requires any pom that is deployed there to reference only artifacts which are also hosted in central. And a project may only use the groupId that is related to that project. So, this only leaves us with one option which is to host these external third-party artifacts using our groupId. The hope is that someday these projects will start using maven and the need for this will no longer be.

Jetty context XML configuration plugin generator helper. This plugin helps you to generate your Context XML file with a dynamic content such as: * classpath entries * web app resources * maven properties Plugin needs a template Jetty context XML file where the dynamic content is injected. Injection of dynamic content is supported as: * altering the DOM with new values * with enabled filtering dynamic values can be replaced as properties (see bellow) Filtering of the template file is supported. Basically it means you can include content from your maven properties in your context XML file. If desired plugin sets two maven properties with the dynamic content: * jetty.conf-plugin.classpath * jetty.conf-plugin.webapp These properties might be used for filtering as well. Plugin resolves project dependency artifacts. These artifacts are transformed into webapp resources and classpath entries. Works with multi-module projects. Works in Eclipse with enabled m2e.