Download JAR files tagged by artifact with all dependencies

The common classes for XMPP and JAXB. The published schemas from xmpp.org are retrieved and compiled into an artifact for each protocol. External projects should depend on the base module + the protocol's they are interested in. All other dependencies are then retrieved automatically by maven.

A bundle project producing JAX-RS RI bundles. The primary artifact is an "all-in-one" OSGi-fied JAX-RS RI bundle (jaxrs-ri.jar). Attached to that are two compressed JAX-RS RI archives. The first archive (jaxrs-ri.zip) consists of binary RI bits and contains the API jar (under "api" directory), RI libraries (under "lib" directory) as well as all external RI dependencies (under "ext" directory). The secondary archive (jaxrs-ri-src.zip) contains buildable JAX-RS RI source bundle and contains the API jar (under "api" directory), RI sources (under "src" directory) as well as all external RI dependencies (under "ext" directory). The second archive also contains "build.xml" ANT script that builds the RI sources. To build the JAX-RS RI simply unzip the archive, cd to the created jaxrs-ri directory and invoke "ant" from the command line.

checker-qual-android contains annotations (type qualifiers) that a programmer writes to specify Java code for type-checking by the Checker Framework. The checker-qual-android artifact is identical to the checker-qual artifact, except that in checker-qual-android annotations have classfile retention. The default Android Gradle plugin retains types annotated with runtime annotations in the main dex, but strips out class-retention annotations.

checker-qual-android contains annotations (type qualifiers) that a programmer writes to specify Java code for type-checking by the Checker Framework. The checker-qual-android artifact is identical to the checker-qual artifact, except that in checker-qual-android annotations have classfile retention. The default Android Gradle plugin retains types annotated with runtime annotations in the main dex, but strips out class-retention annotations.

This artifact provides the implementation of (a blue-fringe version of) the "regular positive negative inference" (RPNI) learning algorithm as presented in the paper "Inferring regular languages in polynomial update time" (https://dx.doi.org/10.1142/9789812797902_0004) by Jose Oncina and Pedro García. More details on the blue-fringe version of this algorithm can be found in the book "Grammatical Inference" (https://doi.org/10.1017/CBO9781139194655) by Colin de la Higuera.

This artifact provides the implementations of various learning algorithms for systems of procedural automata such as the ones described in the papers "Compositional learning of mutually recursive procedural systems (https://doi.org/10.1007/s10009-021-00634-y) and "From Languages to Behaviors and Back" (https://doi.org/10.1007/978-3-031-15629-8_11) by Markus Frohme and Bernhard Steffen.

This artifact provides the integration of the model checker "LTSmin" (https://ltsmin.utwente.nl/) as described in the paper "Sound Black-Box Checking in the LearnLib" (https://dx.doi.org/10.1007/s11334-019-00342-6) by Jeroen Meijer and Jaco van de Pol. Note that this implementation requires a local installation of the LTSmin binaries (see https://ltsmin.utwente.nl/) which are not explicitly included in this artifact due to packaging reasons.

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.