gnodet opened a new pull request, #12159: URL: https://github.com/apache/maven/pull/12159
## Summary Backport of #12157 to `maven-4.0.x`. - When a remote parent POM declares a plugin with an explicit version in `<build><plugins>` (not `<pluginManagement>`), `mvnup`'s plugin upgrade strategy now adds the plugin to **both** `<pluginManagement>` and `<build><plugins>` in the child project - Previously, only a `<pluginManagement>` entry was added, which is insufficient because the parent's `<plugins>` version takes precedence over the child's `<pluginManagement>` Cherry-picked cleanly from master. **Note:** The `InheritedPluginDetectionTests` tests (including `shouldDetectInheritedPluginsFromRemoteParent` which existed before this PR) are pre-existing failures on `maven-4.0.x` — they fail on the base branch without this change as well. ## Test plan - [x] Cherry-pick applied cleanly with no conflicts - [x] All new tests pass on master (verified in #12157) - [x] Pre-existing test failures on 4.0.x confirmed unrelated to this change 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
