[
https://issues.apache.org/jira/browse/MNG-8009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-8009:
---------------------------------
Priority: Major (was: Blocker)
> BOM peculiarities with build ordering
> -------------------------------------
>
> Key: MNG-8009
> URL: https://issues.apache.org/jira/browse/MNG-8009
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
> Affects Versions: 3.9.6, 4.0.0-alpha-10
> Reporter: Tamas Cservenak
> Priority: Major
>
> 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:
> bq. 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_?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
