[GitHub] [openjpa] s4iko opened a new pull request, #101: Log4j2 update to last version (free of vulnerability such as Log4Shell)

[GitBox <gi...@apache.org>]

s4iko opened a new pull request, #101:
URL: https://github.com/apache/openjpa/pull/101

   Hi,
   The fact is that old version of Log4j2 are sometimes filtered by proxies resulting in a build failed due to missing dependency (that alos impact other project depending on this one, such as Camel).
   And in a more global reflection, I think it is better to have a "clean" log4j2 version ;)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@openjpa.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [openjpa] solomax merged pull request #101: Log4j2 update to last version (free of vulnerability such as Log4Shell)

[GitBox <gi...@apache.org>]

solomax merged PR #101:
URL: https://github.com/apache/openjpa/pull/101


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@openjpa.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [openjpa] solomax commented on pull request #101: Log4j2 update to last version (free of vulnerability such as Log4Shell)

[GitBox <gi...@apache.org>]

solomax commented on PR #101:
URL: https://github.com/apache/openjpa/pull/101#issuecomment-1255785283

   Thanks for the contribution @s4iko !


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@openjpa.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org