Hi Thomas, I agree - the only use case would be, that you do not want automatic log detection (in case of log4j 2 enable isLog4jAutoInitializationDisabled) - but then why you want Turbine to initialize it instead?
We could just remove it and it would still work (if log4j2 is enabled). Best regards, Georg Von: Thomas Vandahl <[email protected]> An: Turbine Developers List <[email protected]> Datum: 17.12.2018 17:55 Betreff: Re: turbine archetype and logging configuration problems On 17.12.18 17:40, Georg Kallidis wrote: > Hi Jeffery, > > the diff with one of mine dep trees shows, that you did not get > > org.apache.logging.log4j:log4j-web:jar:2.11.1:compile I always wanted to suggest to remove logging initialization and configuration from the Turbine framework. Experience tells that the integration into containers and other frameworks works better if we try to behave defensively. Most logging frameworks are better configured externally. WDYT? Bye, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
