Download JAR files tagged by someone with all dependencies

Someone forgot to fill this in. See http://stackoverflow.com/questions/38272550/how-to-fail-the-gradle-build-if-subproject-is-missing-a-property

This is a very simple application that is intended to serve as the default page that can be viewed when the server is first installed so that someone can see that the installation is working.

This is a very simple application that is intended to serve as the default page that can be viewed when the server is first installed so that someone can see that the installation is working.

This is a very simple application that is intended to serve as the default page that can be viewed when the server is first installed so that someone can see that the installation is working.

dotenv is a Java library that allows you to access and connect to .env files to store data like tokens, etc. without someone viewing your main class and seeing them.

Interfaces to be implemented by Domains, Connectors and Events which handle intatiation of Services and Proxies, classes for registration of bundles and services, classes for localization, classes that save connector properties (Persistence) and finally classes that enable the web application to have access to OSGI bundles. This bundle contains only the model and interface descriptions of all those services. In theory someone can take only a minor number of openengsb bundles, the api and create the rest of the system on his own.

Interfaces to be implemented by Domains, Connectors and Events which handle intatiation of Services and Proxies, classes for registration of bundles and services, classes for localization, classes that save connector properties (Persistence) and finally classes that enable the web application to have access to OSGI bundles. This bundle contains only the model and interface descriptions of all those services. In theory someone can take only a minor number of openengsb bundles, the api and create the rest of the system on his own.

The Polymorphic DSL test framework was designed to solve the challenges with testing large, complex systems. Modern architecture requires software to run as distrubited systems or on multiple platforms. The conventional cost of testing these systems is quite high. PDSL allows a user to describe the system under test using a DSL of some kind: a picture, sentences in natural languages, graphs, etc. Using a common DSL allows someone to make deeply scalable tests. A simple change to the DSL could generate dozens of tests providing coverage through many layers of the test pyramid or even multiple applications.

A Maven Mojo to download and "degenerate" non-maven projects into sources and binaries This MOJO is supposed to scrape and "de-generate" a zip file containing jars into a project's generated-sources folder, skipping items provided in the `src/` folder. It is intended to "mavenize-with-changes" an existing project and allow the user (of the Mojo) to replace classes which they do not have the ability/desire to recompile without setting up a full build. It can also be used to import non-maven projects by not changing anything. The itch I wanted to scratch was mostly to port libGDX to Maven, while replacing the native methods on Matrix4, without rebuilding the whole project. In essence - it's an alternative to patching someone else's project.

This is the brand new, re-written from scratch plugin for ANTLR v3. Previous valiant efforts all suffered from being unable to modify the ANTLR Tool itself to provide support not just for Maven oriented things but any other tool that might wish to invoke ANTLR without resorting to the command line interface. Rather than try to shoe-horn new code into the existing Mojo (in fact I think that by incorporating a patch supplied by someone I ended up with tow versions of the Mojo, I elected to rewrite everything from scratch, including the documentation, so that we might end up with a perfect Mojo that can do everything that ANTLR v3 supports such as imported grammar processing, proper support for library directories and locating token files from generated sources, and so on. In the end I decided to also change the the ANTLR Tool.java code so that it would be the provider of all the things that a build tool needs, rather than delegating things to 5 different tools. So, things like dependencies, dependency sorting, option tracking, generating sources and so on are all folded back in to ANTLR's Tool.java code, where they belong, and they now provide a public interface to anyone that might want to interface with them. One other goal of this rewrite was to completely document the whole thing to death. Hence even this pom has more comments than funcitonal elements, in case I get run over by a bus or fall off a cliff while skiing. Jim Idle - March 2009