A Maven parent POM is the correct mechanism for sharing common build-plugin configuration across multiple related Mule applications. The reusable portions of the Mule Maven Plugin configuration—such as plugin version, common execution settings, repository conventions, and deployment structure—can be centralized in the parent. Child applications then inherit the configuration while supplying project-specific values through Maven properties.

MuleSoft documentation demonstrates this parent-child inheritance model for Maven plugin configuration, including defining plugins under the parent POM's pluginManagement section so child projects can reference or override the configuration. MuleSoft also describes parent POMs as containing common configuration and defaults used by dependent module projects.

A BOM primarily centralizes dependency versions through dependencyManagement; it is not the appropriate artifact for reusable build/deployment plugin configuration. A project-specific pom.xml would duplicate the same Mule Maven Plugin details across every application. settings.xml, meanwhile, is intended for Maven installation/user-level settings such as repositories, profiles, and credentials rather than distributable project build logic.

Therefore, the Mule Maven Plugin configuration should be centralized in a reusable parent pom.xml.

Reference topics: Maven parent POM; plugin inheritance; Mule Maven Plugin; reusable enterprise build configuration.

Official documentation: https://docs.mulesoft.com/munit/3.0/munit-maven-plugin

Official documentation: https://docs.mulesoft.com/mule-sdk/latest/getting-started

Official documentation: https://docs.mulesoft.com/mule-runtime/4.6/maven-reference

===============================================================