gnodet commented on issue #11606: URL: https://github.com/apache/maven/issues/11606#issuecomment-4777899000
This is likely fixed by the batch of mvnup PRs merged since RC-5, specifically: - **#12165** — Fix mvnup plugin upgrade for versions locked by parent build/plugins - **#12158** — Fix mvnup: use effective model to resolve properties from remote parents The root cause was mvnup not seeing that plugins were already managed by the remote Apache parent POM, and injecting redundant `<pluginManagement>` entries. Could you verify by running current `mvnup apply --model-version 4.1.0` on httpcomponents-client at commit `ee6ebee18`? If the spurious pluginManagement no longer appears, this can be closed. -- 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]
