EE4J Maven Profiles

The EE4J parent pom defines three Maven profiles:

oss-release

Use this profile when publishing artifacts using the Maven release plugin, or when deploying directly. For example:

$ mvn -Poss-release deploy

snapshots

The snapshots profile allows access to Maven SNAPSHOT versions of other artifacts. For example, if project A depends on project B, and project B has published a 1.2.0-SNAPSHOT version, project A can be updated to depend on that version and then the build of project A would use:

$ mvn -Psnapshots install

This is useful during development when related projects are iterating quickly and are not ready to publish a final version. (If all the Maven artifacts are built from the same repository, this is not necessary.)

staging

Similar to the snapshots profile, the staging profile allows access to staged but not yet published non-SNAPSHOT versions of artifacts. As above, if project B stages the 1.2.0 version and project A depends on it, project A can be built with:

$ mvn -Pstaging install

This allows a collect of projects to stage final versions (using the oss-release profile above), test those versions (using this staging profile), and then publish the final versions after testing has completed and the release has been approved. This is particularly useful with GlassFish since this allows external dependencies to be staged, integrated into GlassFish, and tested using the CTS before publishing the staged version.