ppkarwasz commented on issue #3834: URL: https://github.com/apache/logging-log4j2/issues/3834#issuecomment-3085025523
Hi @rob975, It turns out the fix for the `error_prone` issue was ineffective due to an oversight on my part (see #3822). The core problem is that we don’t currently have a dedicated test for this scenario—the closest we have is a log event with `ERROR` severity in the Gradle build (apache/logging-log4j-samples#351). Does your build actually fail because of this, or is it just logging an `ERROR`-level message? I believe this kind of inconsistency between the flattened parent POM and its children will eventually be resolved once we have the opportunity to migrate to Maven 4 (#3780), which handles POM flattening in a more consistent and controlled way. -- 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
