Hi, I noticed a slight change in behavior when upgrading a client's setup from Maven 3.9.11 to 3.9.12.
In this scenario, we start out with an empty .m2/repository and we build the same set of projects in exactly the same way (it's a script). The parent pom is part of the build (built first) and it locks in versions for most Maven plugins. One change I noticed was that plugins that were only part of parent pluginManagement, but not used directly in the set of projects built, were no longer being downloaded. In my clients case, that was maven-assembly-plugin, maven-deploy-plugin, and maven-release-plugin (plus a release artifact). The second difference was that some Maven metadata files were generated, they seem to be pertaining to plugins, that are not generated with 3.911. I looked in the changelog briefly and nothing caught my attention to explain this difference. Also tried downgrading maven-resolver to the version used in 3.9.11, but that made no difference. I was just curious to know if these differences between 3.911 and 3.9.12 are intentional or not? Best regards, Eric L
