> Avalon components which have their own log framework. I yes, this is true. Though you could also provide a custom adapter, which I did in Fulcrum Yaafi Log4j2logger (right where Avalon comes into play, and while Avalon Excalibur provides some adapter implementations itself).
I thought at some point an implementation of this kind is helpful, as Avalon logger framework is not developed anymore, so I decided to provide an helper class, which nowadays users may find useful, hopefully. > dependencyManagement in Turbine Parent POM? This is always a very good idea, instead of use inherited properties, we should follow this IMO .. Best regards, Georg Von: Thomas Vandahl <[email protected]> An: Turbine Developers List <[email protected]> Datum: 15.12.2021 11:12 Betreff: Re: [turbine-parent] 02/02: Update parent for release, set dependency scan for profile apache-release only Hi Georg, > Am 15.12.2021 um 09:05 schrieb Georg Kallidis <[email protected]>: > > The fast fix for everyone is just to replace the log4j libs, we are in > each module at version above 2.14 (> 2.12, which is Java 7 and has a > separate fix), that means it the new ones are binary compatible IMO. Actually, Fulcrum components are Avalon components which have their own log framework. I already tried to fix this a couple of times but the alternative log frameworks keep sneaking in. In a perfect world, Avalon components should not have a dependency on any logging framework implementation at all. > Might be there are better ideas or suggestions or I am missing some > important information? dependencyManagement in Turbine Parent POM? Bye, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
