-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Logger not configured when JAR is started #743
Comments
Problem of log4j2 in fat jars. Cannot be resolved easily. Maybe switch back to log4j v1? |
Do you have a link for it? The stackoverflow answer at http://stackoverflow.com/a/34149368/873282 suggests that we might be using a wrong XML configuration. OK, JIRA-LOG4J2-954 suggests that we should downgrade to 2.0.2. As log4j v1 reached its end of life August 2015, I would suggest to try to get log4j v2 running or switch to Logback ^^. |
Commons-logging does not work well with logback. Solution in the maven world https://github.com/edwgiz/maven-shaded-log4j-transformer |
Still present in 5.0's "Portable Linux" . Java: openjdk version "1.8.0_252" |
When starting the JAR of JabRef, following output appears:
Steps to reproduce:
gradlew shadowJar
java -jar build\libs\JabRef-3.3dev-fat.jar
The text was updated successfully, but these errors were encountered: