On Thu, Jan 10, 2019 at 2:53 PM Rainer Jung <rainer.j...@kippdata.de> wrote:
> Am 10.01.2019 um 13:16 schrieb Rémy Maucherat: > > On Thu, Jan 10, 2019 at 1:09 PM Mark Thomas <ma...@apache.org> wrote: > > > >> There is the possibility that an alternative logging JAR could return. > >> https://markmail.org/message/gdmffcyporhcmqge > >> > >> Whether that needs an optional / alternative JAR or whether it could be > >> handled via configuration is TBD. > >> > > > > Ok, so I'm not doing anything immediately but I'll put my patch in a BZ > > instead. It does remove a chunk of build.xml, which is good. > > In the meantime Log4J2 (I think starting with 2.10.0) added the artefact > log4j-appserver.jar and support for an additional config file > log4j2-tomcat.xml: > > https://logging.apache.org/log4j/2.x/log4j-appserver/index.html > > That allows for clean integration, so I currently do no longer see a > need for an alternative JULI jar. > Ok. I find the proposed setup rather lame looking however. log4j2/[lib|conf] + modify classpath ? It should be in bin and conf respectively to blend in, but adding to the classpath manually is still needed (bad). Rémy
