Oops, sent too soon. I see that’s a snapshot repo. I believe we need to run CI again since we purged some old snapshots the other day.
On Tue, Nov 3, 2020 at 08:23 Matt Sicker <boa...@gmail.com> wrote: > Snapshots aren’t meant to be in the release repository. While we do > publish snapshots in our snapshots repo from CI, those aren’t releases, so > we don’t directly advertise them except to users who want to test out > future changes. I’m not particularly sure why you’ve chosen 3.x as that > repo changes more drastically than the 2.x one (except for the API module). > > On Tue, Nov 3, 2020 at 05:35 Oliver Kopp <kopp...@gmail.com> wrote: > >> Hi, >> >> Due to >> https://issues.apache.org/jira/browse/LOG4J2-2690?focusedCommentId=16927936&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16927936 >> we are using 3.0.0-SNAPSHOT in our Java 15 project. >> >> This morning, we noticed that maven-metadata.xml disappeared from >> >> https://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-jcl/3.0.0-SNAPSHOT/ >> and all mirrors. This makes our software JabRef >> (https://github.com/jabref/jabref/) non-buildadble. >> >> Would it be possible to bring back 3.0.0-SNAPSHOT to the apache maven >> repository? >> >> Thank you in advance and greetings, >> >> Oliver >> -- >> https://github.com/koppor/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org >> For additional commands, e-mail: log4j-user-h...@logging.apache.org >> >>
