Maven Enforcer Plugin and Blue-Green Deployment Artifact Consistency

Ensuring binary compatibility during a blue-green migration requires strict control over the artifact's classpath. While Maven handles build automation, its 'nearest-definition' resolution strategy for transitive dependencies can lead to version drift if the dependency graph is modified between the legacy and new build cycles.

The goal is to prevent runtime linkage errors by ensuring that the resolved dependency tree remains identical across different environment profiles. There is uncertainty regarding how to best leverage the Maven Enforcer Plugin to lock transitive versions without manually declaring every single dependency in the project object model (POM).

Which Enforcer rules are most effective for detecting unplanned changes in the transitive dependency hierarchy during a migration? How can these rules be integrated into a multi-profile build to ensure the 'green' artifact maintains strict version parity with the 'blue' artifact?