Download JAR files tagged by poms with all dependencies

This project contains reusable maven parent poms and maven project archetypes with sensible defaults, for example pre-configured with the latest maven plugin versions or already defining some common libraries as dependencies (commons-lang, guava, etc).

A POM that can be extended by all POMs that use the ear packaging type. It extends the main uberpom because EAR files don't contain Java source code so we do not want to inherit all the reporting and other settings from the JAR Uber POM, which are not necessary and would just slow the build down.

While most bundles work quite find with the typical wrapped bundle code from poms/wrapped there are some special cases where it does not work this way. This parent contains all bundles which are not meant to be wrapped in the classical way, but require some additional, special work.

This module defines a standard parent POM to use for various Incode applications and modules. Its primary purpose is to make it easy to use a set up maven mixins (https://github.com/odavid/maven-plugins) within child POMs. Specifically this means locking down the versions of plugins using pluginManagement. It does NOT define any mixins for Apache Isis.

This module defines a standard parent POM to use for various Incode applications and modules. Its primary purpose is to make it easy to use a set up maven mixins (https://github.com/odavid/maven-plugins) within child POMs. Specifically this means locking down the versions of plugins using pluginManagement. It does NOT define any mixins for Apache Isis.

This module defines a standard parent POM to use for various Incode applications and modules. Its primary purpose is to make it easy to use a set up maven mixins (https://github.com/odavid/maven-plugins) within child POMs. Specifically this means locking down the versions of plugins using pluginManagement. It does NOT define any mixins for Apache Isis.

The goal of this module is to be able to deploy all the db driver jars to all environments instead of needing to change parent pom properties and rebuilding for each environment. The same effect used to be accomplished by manually updating all related poms with hardcoded dependencies, this module allows for just one place to be updated and the change propogates to all the packaged modules/portlets.

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.

Geronimo integration testsuite. This contains 2 profiles, default and child. The default profile is used by the top level suites directly under this. The child profile is used by the test poms under the suites. This pom defines the basic dependencies needed by most suites. The start-selenium, start-server, invoke, and stop-server goals are globally configured here in the pluginManagement sections. They just need to be bound in the suites where needed and appropriate. The test poms under the suites should have this pom as their parent and set their relativePath appropriately The test poms under the suites inherit an empty 'child' profile from here. But any other build executions within the test poms should all be inside a 'child' profile.