I’d like to get a fix for LOG4J2-2954 into this release so appenders are flushed before the jvm exits. I’ll be reviewing the proposed fix and making required changes tonight or tomorrow if that’s alright.
-ck > On Nov 1, 2020, at 8:10 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > > Over at Apache Commons, I just released VFS, and it too is full of > snapshots: > > https://repository.apache.org/content/groups/public/org/apache/commons/commons-vfs2/ > > Either we have all been doing releases wrong, the tooling is wrong, or our > understanding of > > https://repository.apache.org/content/groups/public/ > > Vs. > > https://repository.apache.org/content/groups/snapshots/ > > Vs. > > https://repository.apache.org/content/groups/staging/ > > Is wrong... darn. > > Gary > >> On Sun, Nov 1, 2020, 08:05 Gary Gregory <garydgreg...@gmail.com> wrote: >> >> Very odd indeed, the public (non-snapshot) repository is full of snapshots: >> >> >> https://repository.apache.org/content/groups/public/org/apache/logging/log4j/log4j-core/ >> >> Gary >> >>> On Sun, Nov 1, 2020, 00:51 Ralph Goers <ralph.go...@dslextreme.com> wrote: >>> >>> I started the process of preparing for the release today. The Maven site >>> build is failing because somehow a version named 2.14.0—SNAPSHOT was >>> uploaded to the Nexus Snapshot repository. While investigating I noticed >>> that there is at least one snapshot for every past release so Nexus >>> apparently is not configured to delete snapshots after a release is >>> performed. >>> >>> I’ve asked in Slack to have all the snapshots under logging be deleted >>> but I suspect I will need to create a Jira issue. In my experience Jira >>> isn’t especially quick about acting on these so I don’t know when I will be >>> able to proceed. Matt or Gary, if you have more karma then me for some >>> reason please see what you can do. >>> >>> Ralph >>> >>
