infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Orlina (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16834) Log4j 2.11.1 was not published to Maven Central
Date Mon, 30 Jul 2018 14:36:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-16834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561982#comment-16561982
] 

Joel Orlina commented on INFRA-16834:
-------------------------------------

This appears to be a part of a backlog in released artifacts that started on the 25th when
we switched some of our sync processing to new infrastructure.  We ran catchup jobs on the
26th and 27th, but it appears that certain artifacts we're still missed.  We're continuing
to investigate, but, in the meantime, I'll submit these artifacts for a manual re-sync.

> Log4j 2.11.1 was not published to Maven Central
> -----------------------------------------------
>
>                 Key: INFRA-16834
>                 URL: https://issues.apache.org/jira/browse/INFRA-16834
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Nexus
>            Reporter: Ralph Goers
>            Priority: Major
>
> Log4j 2.11.1 was released on the evening of July 25. It shows up in the releases repository
at repository.apache.org, but it has not yet appeared in the Maven Central repository.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message