dhruv9b commented on PR #1024: URL: https://github.com/apache/maven-enforcer/pull/1024#issuecomment-5644943461
> Contributor Yes, the report plugin version is provided through `<build><pluginManagement>`, but it is intentionally not specified explicitly under `<reporting><plugins>`. This matches the configuration from the original #916 reproducer. Maven allows the reporting plugin version to be resolved from `<build><pluginManagement>` when it is not specified in `<reporting>`. The issue is that `RequireSameVersions` was seeing the report artifact with version `RELEASE`, while the corresponding build plugin was `3.5.3`, even though the report plugin was managed at `3.5.3`. So the integration test intentionally leaves the reporting version unspecified to reproduce that exact case. The fix uses the managed version when no explicit reporting version is present. -- 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]
