[
https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693694#comment-17693694
]
Jon Wilmoth edited comment on LOG4J2-3650 at 2/26/23 8:26 PM:
--------------------------------------------------------------
Thank you [~rgoers]. We use the ListAppender in our narrow integration tests
to verify sensitive values aren't logged by our code or 3rd party libs. I can
confirm the new coordinates are available and work in our existing tests after
adjusting the import from `
org.apache.logging.log4j.test.appender.ListAppender` to
`org.apache.logging.log4j.core.test.appender.ListAppender`.
was (Author: [email protected]):
Thank you [~rgoers]. We use the ListAppender in our narrow integration tests
to verify sensitive values aren't logged by our code or 3rd party libs. I can
confirm the new coordinates are available and work in our existing tests after
adjusting the package from `
org.apache.logging.log4j.test.appender.ListAppender` to
`org.apache.logging.log4j.core.test.appender.ListAppender`.
> Release 2.20.0 missing artifacts
> --------------------------------
>
> Key: LOG4J2-3650
> URL: https://issues.apache.org/jira/browse/LOG4J2-3650
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.20.0
> Reporter: Jon Wilmoth
> Priority: Major
>
> It looks like the new 2.20.0 release didn't publish the
> log4j-core-<version>-tests.jar files that were in the previous release. Can
> these files be published?
> # https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-core/2.19.0/
> # https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-core/2.20.0/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
