Hi John, I say go for it! And thanks for jumping in here. I do request that any changes are discussed on the fortress mailing list.
Regards, — Shawn > On Jun 13, 2020, at 3:40 AM, john eipe <[email protected]> wrote: > > I have been part of the mailing list for quite some time but never really got > a chance to contribute except in stackoverflow. > > I'm familiar with log4j2 migration and I can take up this improvement task if > nobody else has started on it. > > Regards, > John Eipe > > “The Roots of Violence: Wealth without work, Pleasure without conscience, > Knowledge without character, Commerce without morality, Science without > humanity, Worship without sacrifice, Politics without principles” > - Mahatma Gandhi > > > On Thu, 11 Jun 2020 at 21:09, Shawn McKinney (Jira) <[email protected]> wrote: > Shawn McKinney created FC-286: > --------------------------------- > > Summary: To Apache Log4j 2 > Key: FC-286 > URL: https://issues.apache.org/jira/browse/FC-286 > Project: FORTRESS > Issue Type: Improvement > Affects Versions: 2.0.5 > Reporter: Shawn McKinney > Assignee: Shawn McKinney > Fix For: 3.0.0-RC1 > > > Upgrade to Log4j 2, due to vulnerabilities such as: > > [https://github.com/advisories/GHSA-2qrg-x229-3v8q] > > > > in the old libs. > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
