Gary, you haven't replied to this question of mine yet. I'd like to know more about your use case.
I had a call with Ralph and he stated `log4j-server` is not usable without customizations. Hence, he added, it is better suited to `log4j-samples`. I liked this idea. Do you have any objections if we archive the `log4j-server` and move its content to `log4j-samples` instead? On Wed, Sep 13, 2023 at 3:16 PM Volkan Yazıcı <vol...@yazi.ci> wrote: > > The project doesn't have any releases, how do you use it at work? Note that > once they are retired (i.e., archived) you will still have access to the > sources. > > On Wed, Sep 13, 2023 at 3:06 PM Gary Gregory <garydgreg...@gmail.com> wrote: >> >> Yes, we use logging-log4j-server at work. >> >> Gary >> >> On Wed, Sep 13, 2023 at 8:15 AM Volkan Yazıcı <vol...@yazi.ci> wrote: >> > >> > I propose retiring `logging-log4j-server` >> > <https://github.com/apache/logging-log4j-server> and `logging-log4j-audit` >> > <https://github.com/apache/logging-log4j-audit> repositories (which never >> > had any releases) and making it clear in their READMEs that these >> > repositories exist only for archival purposes. Objections?
