[
https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692254#comment-17692254
]
Ralph Goers commented on LOG4J2-3650:
-------------------------------------
This is going to be a bit of a long answer.
The work on Log4j 3.0 in our master branch is targeted at fully supporting
JPMS. Due to how JPMS works and at the recommendation of the Maven team we
were forced to move the tests into their own modules. So we now create
log4j-api-test and log4j-core-test jars as primary artifacts. Of course,
because the unit tests need those classes they had to be moved to those test
projects. Over time it became more and more difficult to keep the work on Log4j
3 in sync with the 2.x work. We reconciled this by separating the tests out in
2.x just as we have done in master.
The bottom line is that the test jars for log4j-api and log4j-core are still
being published. But their coordinates have changed from log4j-api-2.x.x-test
to log4j-api-test-2.x.x. Please adjust your poms.
> 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)
