Yes, Nexus indicates the bad snapshot was pushed by “CI Hudson” in May.
Ralph > On Nov 1, 2020, at 8:23 AM, Matt Sicker <boa...@gmail.com> wrote: > > Are these snapshots any different from the ones being pushed by our old > Jenkins config? That’s another possibility. I think you’re right about the > repo groups though since that’s how Nexus works. > > On Sun, Nov 1, 2020 at 09:21 Apache <ralph.go...@dslextreme.com> wrote: > >> The public repo is most likely a group repo configured with both the >> release repo and the snapshot repo.that way by configuring Maven to use the >> public repo builds can access both releases and snapshots. But all the >> snapshots only exist in the snapshot repo. >> >> Ralph >> >>> On Nov 1, 2020, at 6:08 AM, 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 >>>> >> >> >>
