-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
ERROR StatusLogger Log4j2 could not find a logging implementation. #5475
Comments
JabRef 5.0.0-dev--2019-10-18----bc26c3ac5 I can confirm this "issue". As mentioned by @bernhard-kleine I do not know, whether the error is an actual problem, since JabRef starts flawlessly. As explained by @tobiasdiez the console starts due to a limitation of the software that is used to created the installer: #5468 (comment) |
We also have a ticket open at the log4j guys. |
the version from 2019-08-25 didnot show the console. What has changed inbetween? |
@bernhard-kleine : See here and here: |
To make is explicit (especially for me): The issue with the console is described here #5474. |
Yes
Am 2. Februar 2020 15:03:42 MEZ schrieb Oliver Kopp <[email protected]>:
…The issue with the console is described here
#5474. (Right?)
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#5475 (comment)
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
|
Refs https://issues.apache.org/jira/browse/LOG4J2-2690 |
neither does 2019-04-19 or 2010-09-16 has the black console problem |
@digdig: |
@AEgit Does the explained reason say something about why previous versions are OK and no consoles? |
We switched to a new installer, we now use the native Java packager to create custom versions for each OS. This enables us to directly build native packages/installer for each OS |
Which version is supposed the new version, since the snapshot is still from 2020-06-02? |
@bernhard-kleine Which new version are you talking about? Is this relevant to this issue? |
I would like to know whether the snapshot from 2020-06-02 has already the new installer or not. Since the statusLogger error is the only thing which is not ok as far as I see, I donot want to download every new snapshot. Maybe you can understand. |
You opened the issue yourself (#5475 (comment)) - the new installer has been part of the JabRef dev version since (at least) JabRef 5.0.0-dev--2019-10-18----bc26c3ac5 There is no other current dev version out there, without this "new" installer (at least I am not aware of it). Do I misunderstand you? |
Then I have Christoph misinterpreted. I seemed to me that as of today there was a new installer. Sorry for the noise. |
The problem is that Log4j2 is simply not compatible with Java 9. I've created a very simple Java 9 application which shows this problem: https://github.com/tobiasdiez/javatestbed. |
I do not habe the console log anymore in the latest version: JabRef 5.0-beta.457--2020-02-22--d38f813 |
JabRef 5.0-beta.458--2020-02-23--b2ab177 I can confirm that there is any console any further. Thanks a lot. Could be closes! :D |
Sadly, the bug is still there - it's only not displayed anymore because the console window is hidden. For the same reason, the Error console is currently not working (nothing is shown there). |
This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs. As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:
Thank you for your contribution! |
@tobiasdiez , @Siedlerchr Is this issue with the Log4j2 resolved, then this should be closed, otherwise it should remain open, even its last activity was 6 months ago. |
I think the issue is still present in: JabRef 5.2--2020-11-07--df80c13 |
Yep, issue is still here, apache log4j team did not fix it yet. Were thinking of switching to another log framework maybe. |
This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs. As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:
Thank you for your contribution! |
JabRef 5.3--2021-06-08--9d1c448 I think the issue is still present in the current dev version. |
JabRef 5.0.0-dev--2019-10-18----bc26c3ac5
Windows 7 6.1 amd64
Java 12.0.2
Steps to reproduce the behavior:
ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
Log File
The text was updated successfully, but these errors were encountered: