ppkarwasz commented on issue #3779: URL: https://github.com/apache/logging-log4j2/issues/3779#issuecomment-3065139812
Hi @MartyIX, Thank you for the detailed feedback. The resolution of the `com.google.errorprone:error_prone_annotations` dependency in the **consumer** POM (as opposed to the **build-time** POM) remains broken due to the flattening mechanism I described above. Although PR #3785 was intended to address this issue, it turned out to be ineffective—so I've reopened this issue. For a detailed analysis of what went wrong, see #3822. Since this issue cannot be detected by our current [Gradle Integration Test](https://github.com/apache/logging-log4j-samples/tree/main/log4j-samples-gradle-metadata), would you be open to extending that test to also verify transitive dependencies declared in the `provided` Maven scope? Notably, the [Maven Model Builder](https://maven.apache.org/ref/3.9.10/maven-model-builder/) has no trouble resolving the effective model for `log4j-core`, so it seems that Gradle is applying stricter checks that expose this discrepancy. -- 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: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
