I don't know what was our earlier policy on test JARs (if we have any at
all), but I suggest we stop deploying to Nexus anything that is not meant
for public consumption: api, core, adapters, filters, etc. Now are we
supposed to spend hours fixing the tests of an individual because he
happened to depend on Log4j tests?
---------- Forwarded message ---------
From: Jon Wilmoth (Jira) <j...@apache.org>
Date: Tue, Feb 21, 2023 at 10:31 PM
Subject: [jira] [Created] (LOG4J2-3650) Release 2.20.0 missing artifacts
To: <notificati...@logging.apache.org>
Jon Wilmoth created LOG4J2-3650:
-----------------------------------
Summary: 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
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)
