Hi, Sure. I think, we thought, fixing snapshot usage issues (and possibly report back issues) would help log4j more than staying with a pinned snapshot.
Surely, this will cause troubles when initiating a release for Debian. Maybe a 3.0.0 release happens before all other dependencies of our project are packaged for Debian 😅 Cheers, Oliver Ralph Goers <ralph.go...@dslextreme.com> schrieb am Di., 3. Nov. 2020, 16:52: > Snapshots are not releases and we don’t guarantee we won’t make breaking > changes. If you want to use 3.0.0 in a production environment you should > clone the repo locally and create a tag and create an internal release for > yourself. You should also use a version number that won’t conflict with > our releases by using a version number like 3.0.0-mycorp-1. > > Ralph > > > On Nov 3, 2020, at 4:34 AM, 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 > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > >
