ERROR StatusLogger Log4j2 could not find a logging implementation.

[bernhard-kleine]

JabRef 5.0.0-dev--2019-10-18----bc26c3ac5
Windows 7 6.1 amd64
Java 12.0.2

• [+] I have tested the latest development version from http://builds.jabref.org/master/ and the problem persists

Steps to reproduce the behavior:

1. When opening jabref a console starts with this error message
   ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
2. Then Jabref opens still. I do not know what the effect of this error will be.
3. ...

Log File

Paste an excerpt of your log file here

[AEgit]

JabRef 5.0.0-dev--2019-10-18----bc26c3ac5
Windows 10 10.0 amd64
Java 12.0.2

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)
There is already a ticket open to remove the console window:
#5474

[Siedlerchr]

We also have a ticket open at the log4j guys.
It should not be a problem for n the user as JabRef works with it.

[bernhard-kleine]

the version from 2019-08-25 didnot show the console. What has changed inbetween?

[AEgit]

@bernhard-kleine : See here
#5468 (comment)

and here:

#5475 (comment)

[koppor]

To make is explicit (especially for me): The issue with the console is described here #5474.

[bernhard-kleine]

Yes Am 2. Februar 2020 15:03:42 MEZ schrieb Oliver Kopp <notifications@github.com>:

…

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.

[Siedlerchr]

Refs https://issues.apache.org/jira/browse/LOG4J2-2690
Refs also #5226

[digdig]

the version from 2019-08-25 didnot show the console. What has changed inbetween?

neither does 2019-04-19 or 2010-09-16 has the black console problem

[AEgit]

@digdig:
See the comments in this thread (and elsewhere) - the reason has already been explained.
#5475 (comment)
#5468 (comment)

[digdig]

@AEgit Does the explained reason say something about why previous versions are OK and no consoles?
If it has explained, why not roll back to the previous versions?

[Siedlerchr]

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
And there is currently a bug in one of our external dependencies in combination with the new installation system.

[bernhard-kleine]

Which version is supposed the new version, since the snapshot is still from 2020-06-02?

[AEgit]

@bernhard-kleine Which new version are you talking about? Is this relevant to this issue?

[bernhard-kleine]

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.

[AEgit]

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?

[bernhard-kleine]

Then I have Christoph misinterpreted. I seemed to me that as of today there was a new installer. Sorry for the noise.

[jorgman1]

I do not habe the console log anymore in the latest version:

JabRef 5.0-beta.457--2020-02-22--d38f813
Windows 7 6.1 amd64
Java 13.0.2

[bernhard-kleine]

JabRef 5.0-beta.458--2020-02-23--b2ab177
Windows 10 10.0 amd64
Java 13.0.2

I can confirm that there is any console any further. Thanks a lot. Could be closes! :D

[tobiasdiez]

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).

[github-actions]

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:

• If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
• Provide further steps or information on how to reproduce this issue.
• Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
• If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!

[bernhard-kleine]

@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.

[AEgit]

I think the issue is still present in:

JabRef 5.2--2020-11-07--df80c13
Linux 5.4.0-53-generic amd64
Java 15.0.1

[Siedlerchr]

Yep, issue is still here, apache log4j team did not fix it yet. Were thinking of switching to another log framework maybe.

[github-actions]

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:

• If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
• Provide further steps or information on how to reproduce this issue.
• Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
• If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!

[AEgit]

JabRef 5.3--2021-06-08--9d1c448
Windows 10 10.0 amd64
Java 16.0.1
JavaFX 16+8

I think the issue is still present in the current dev version.

[koppor]

Yep, issue is still here, apache log4j team did not fix it yet. Were thinking of switching to another log framework maybe.

In 2021, I am fan of tinylog in contrast to 2017, where I tried to convince people to use jcabi: #3015