Download JAR files tagged by plugin with all dependencies

JTB is a syntax tree builder to be used with the Java Compiler Compiler (JavaCC) parser generator. JTB was originally developped at UCLA up to version 1.3.2 (http://compilers.cs.ucla.edu/jtb/) or (http://compilers.cs.ucla.edu/jtb/jtb-2003/). It has been upgraded in version 1.4.0+ (2009-2010), as an embedded tool within the SourceForge Eclipse JavaCC plugin. It is now (2011) provided as a standalone tool in the same hosting environment as JavaCC.

The maven-dependency-versions-check-plugin is a Maven plugin that verifies that the resolved versions of dependencies are at least the versions specified by the dependencies (or their dependencies etc.) if not higher. More specifically, it will check that * The resolved version of every dependency declared explicitly in the current POM is the same or a newer one than what was stated. If the resolved version has a higher major version number than the declared version, then the plugin will issue a warning if configured to do so. Note that enforced declared versions are ignored by the plugin. * For every explicitly declared dependency in the current POM, all its dependency versions are met. I.e. the resolved versions for all dependencies in that dependency's POM are the same or higher than the one stated in that dependency's POM. This is basically the same check as the one above, but using the dependency's POM! Also, if the current POM has exclusions specified for the dependency, then these transitive dependencies are ignored when checking this particular dependency.

Clirr is a tool that checks Java libraries for binary and source compatibility with older releases. Basically you give it two sets of jar files and Clirr dumps out a list of changes in the public API. The clirr-maven-plugin can be configured to break the build, if it detects incompatible api changes. In a continuous integration process, the clirr-maven-plugin can automatically prevent accidental introduction of binary or source compatibility problems. Additionally, the plugin can generate a report as part of the generated site.

A Maven plugin that installs the AppNeta Java instrumentation agent. Can be used within a pom or directly from command line. The supported goals are "install-agent" and "download-agent". The configuration properties are "agentVersion", "agentLocation" and "agentOperatingSystem"(the last one is only valid for "download-agent" goal), all are optional and may be specified as maven configuration properties or system properties. For other information on our Java agent please visit https://docs.appneta.com/java.

Knowledge Flow plugin that provides a Knowledge Flow step that wraps around a Groovy script. The plugin generates a fully compilable template Groovy script that implements various Knowledge Flow interfaces. The user can fill in the methods that are necessary to accomplish the desired logic. The script is compiled at runtime and the Groovy component passes incoming events to the script and collects and passes on generated events.

The aggregator of the 'CI Police' Maven plugin, whose responsibility is to validate Wix Open Source Projects. These validations includes: * Maven POM requirements (e.g., non-blank 'artifactId') * Sonatype requiremetns (e.g., 'scm') * Wix requirements (e.g., 'organization' populated with Wix details) It is consisted two modules: one, is the main module of the plugin, and the other, is a tests module. The reason for having a tests module is that the tests actually runs the plugin. It is therefore expected to be found in Maven's local repository (at least in the local repository); hence, the separation.

This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module. Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars. Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the subsystem-templates by wildfly-server-provisioning-maven-plugin.

Maven plugin leveraging the baselining feature of the bnd library[0]. The plugin automatically checks an OSGi bundle's package export versions need to be incremented, in accordance with semantic versioning[1,2]. [0] http://blog.osgi.org/2013/09/baselining-semantic-versioning-made-easy.html [1] http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf [2] http://semver.org/spec/v2.0.0.html

This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module. Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars. Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the subsystem-templates by wildfly-server-provisioning-maven-plugin. Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.