vy commented on PR #3450: URL: https://github.com/apache/logging-log4j2/pull/3450#issuecomment-2671859004
> If it fits, the [sample Gradle project](https://github.com/jjohannes/gradle-demos/tree/main/log4j-metadata) I created could be moved to `log4j-samples`. I added a check that asserts what is ending up on the classpaths if you only add the `log4j-api`. So running `./gradlew build` on that sample would be a quite good "end-to-end" test for the metadata publishing. @jjohannes, sounds plausible, thanks! We can run `./gradlew build` either as a part of the `integration-test.yaml` workflow, or add it under a Maven module and run the command (using `antrun-maven-plugin`?), etc. @ppkarwasz, WDYT? -- 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
