-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider change Log4j 2 to Logback because graalvm native build #7486
Comments
Hey thanks for raising. I'm not sure we've really got time to switch libraries without some kind of major issue, there's quite a lot of plumbing involved in changing over. Having said that, have you considered using the log4j api? there's a documented example I'll talk it over with the team and see what options we have... |
Currently the main concern is existing log4j configuration, apart from the issue of changing. This may end up on the backlog because of that until we do more investigation. In the mean time, let us know if you had any luck with referencing via api? |
@rolfyone thanks, I am doing investigation, will feedback once I found the deep issues. |
This is not works. But I found though no log print, it actual no impact for running. I post an issue with jvm-libp2p which may be the underlying problem we came across. |
Hi @GrapeBaBa have you tried the suggestion in micronaut-projects/micronaut-core#6041 to use |
Let me try it |
Closing this issue because of no activity. Will consider reopening if issue is still relevant. |
We are working on https://github.com/optimism-java/hildr which is OP rollup client written in Java. For support p2p feature, we introduce teku as dependency, we used discV5 service discovery and libp2p gossip. It works well when compile with jar, however it not works with graalvm native build.
We found the issue is from Log4j 2 which still not support native build. The issue is here . Would we consider use logback as logging framework?
The text was updated successfully, but these errors were encountered: