[MNG-8009] BOM peculiarities with build ordering

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.9.6, 4.0.0-alpha-10
• Component/s: Inheritance and Interpolation
• Assignee: Unassigned
• Reporter: Tamas Cservenak
• Created: 11/Jan/24 17:22
• Updated: 22/Oct/24 19:52

Description

Maven 3.9.6 and 4.0.0-alpha-11-SNAP (current master), Java 21.

After this commit: https://github.com/apache/maven/commit/f1c53cbfdfc99cfc6e1521a450adeeb817b89345

Executing from top level command mvn spotless:apply does NOT work: plugin is not found!

If you checkout commit before that one, it works.

Diffing the debug output from two executions, the "good" one (before given commit) has this line:

Resolved plugin prefix spotless to com.diffplug.spotless:spotless-maven-plugin from POM org.apache.maven:maven-bom:pom:4.0.0-alpha-11-SNAPSHOT

Meaning, plugin is resolved from BOM??? And as given commit changes the BOM parent from maven-parent (that has spotless defined) to ASF parent (that does not have it), makes plugin not resolvable?

Despite root POM of Maven parent maven-parent defines it, and even top level POM redefines it?

Issue Links

• is caused by: MNG-8003 Maven BOM should have a cleaner parent
• is related to: MNG-8012 Warn on BOM import within same reactor
• relates to: MNG-8191 [reactor build order] modules used in dependencyManagement-section with scope import should be ordered first