View on GitHub

PME @ Red Hat

Standardize Your Builds

Plugin Manipulation


PME can align plugin versions and configuration using a similar pattern to dependencies. It also has the ability to standardize the use of skip flags that determine whether the maven-install-plugin and maven-deploy-plugin execute. Finally, by default PME will inject plugin executions for the project-sources-maven-plugin and buildmetadata-maven-plugin, in order to promote reproducibility of the project build.

Plugin Alignment

NOTE : Several configuration flags are shared with Dependency Manipulator.

Plugin Source


There are two sources of plugins used to align to in PME. The property pluginSource is used to alter the behaviour of how PME handles the multiple sources of plugin information. The BOM value is that PME will use the BOM (i.e. Remote POM) source. Alternatively the REST source may be specified to use only the REST Endpoint information. However by setting the property to either RESTBOM or BOMREST it will instead merge the two sets of values. With RESTBOM precendence is given to the REST information and for BOMREST precendence is given to the BOM information.

Note: If this is not specified the default value for pluginSource will match the value for dependencySource. Therefore it is only necessary to set pluginSource if a different value to dependencySource is needed.

Remote POM

A remote plugin management POM is used to specify the plugin versions (and configuration) to inject:

mvn install -DpluginManagement=org.jboss:jboss-parent:10

This will inject all <pluginManagement/> versions, executions and configuration from the remote POM into the local POM. As with dependency management, multiple remote plugin management POMs can be specified on the command line using a comma separated list of GAVs. The first POM specified will be given the highest priority if conflicts occur.

mvn install,
REST Endpoint

For information on the REST Endpoint see here

Direct/Transitive Dependencies

By default the extension will inject all plugins declared in the remote BOM. If the option overrideTransitive is set to false to then only plugins used will be overridden.

mvn install -DoverrideTransitive=false

Note: overrideTransitive is also used by the Dependency Manipulator.

Strict Mode Version Alignment

For information on strict mode configuration see here


If there is an existing local configuration then it will be merged with the remote. The following configuration controls the precedence:


Default is REMOTE which means the remote configuration takes precedence over local.

If when attempting to merge the remote execution blocks into local, the <id>’s clash an exception will be thrown.

NOTE : As of PME 2.13 (October 2017) the default for injectRemotePlugins has changed from true to false. This option and the corresponding functionality is now marked as deprecated and may be removed in a future release.

If injectRemotePlugins is set to true, PME will also inject any <plugin/> that has execution or configuration sections found in the remote BOM.

Install and Deploy Skip Flag Alignment

By default, this extension will disable the skip flag on the install and deploy plugins. This is useful for build environments that compare the results of install with those from deploy as a validation step. More generally, suppressing installation or deployment tends to be an aesthetic decision that can have subtle functional consequences. It’s usually not really worth the hassle.

This feature does support four modes for alignment, controlled via the enforceSkip (Deprecated property enforce-skip) command-line property:

  1. none - (default) don’t do any alignment
  2. on - (aliased to true) enforce that the skip flag is enabled, suppressing install and deploy functions of the build (useful mainly for module-specific overrides. See below)
  3. off - (aliased to false) enforce that the skip flag is disabled and that install/deploy functions will execute normally
  4. detect - detect the flag state of the install plugin in the main pom, and adjust any other install- or deploy-plugin references to make their skip flag values consistent. Install plugin declarations in profiles are not considered during detection.

Additionally, the feature supports per-module overrides, which can be specified as:|on|true|off|false|detect)

Plugin Removal

If the property pluginRemoval (Deprecated property plugin-removal) is set, PME will remove the specified plugins from the POM files. The argument should be a comma separated list of group:artifact. For example:


Project Sources / Build Metadata Plugin Injection

The extension will inject an execution of project-sources-maven-plugin and build-metadata-plugin by default. This will result in an archive being created containing all project sources after this extension has made any modifications to the pom.xml’s. The archive will only be created in the execution-root project, and will be attached for installation and deployment using the project-sources classifier. The metadata plugin will create a file containing information (e.g. the command line) on the invoked project. This will also be included in the archive tar.

Note: this manipulator will only be active by default if one or more other manipulators have been activated.

To skip injection of the sources and metadata plugins, you can use the properties projectSrcSkip (Deprecated property project.src.skip) and projectMetaSkip (Deprecated property project.meta.skip):

mvn install -DprojectSrcSkip=true
mvn install -DprojectMetaSkip=true

If unspecified, default versions of the project sources and metadata plugins will be injected (currently, version 0.3 and 1.5.0 respectively). To gain more control over this injection, you can specify the versions for project sources and metadata plugins with the properties projectSrcVersion (Deprecated property project.src.version) and projectMetaVersion (Deprecated property project.meta.version):

mvn install -Dproject.src.version=x.y
mvn install -Dproject.meta.version=x.y