Bug 578109 - Failed to load class "org.slf4j.impl.StaticLoggerBinder"
Summary: Failed to load class "org.slf4j.impl.StaticLoggerBinder"
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.23   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 579655 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-01-08 00:29 EST by BS FU CLA
Modified: 2022-04-11 19:48 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description BS FU CLA 2022-01-08 00:29:27 EST
Try eclipse "2021-12 R", install 2 package Eclipse for C/C++ and for RCP and RAP Developers on Windows10/Ubuntu20.04 host, launch eclipse from command line.
It reports the following err at the beginning.

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

And we can WA this err according to the guide http://www.slf4j.org/codes.html#StaticLoggerBinder, but it's unreasonable to WA on a basic released eclipse that show err in launch.
Comment 1 Rolf Theunissen CLA 2022-01-10 03:56:32 EST
org.slf4j.api is required by requirements of platform. However, no implementation backend is provided.
This causes this warning (or notification) to be printed, and defaulting to NOP is the valid behavior. However, should this backend be provided by Platform or should it be included in EPP to provide a valid product?
Comment 2 Thomas Wolf CLA 2022-01-10 05:37:59 EST
See also bug 549869. It's not that simple.
Comment 3 Rolf Theunissen CLA 2022-01-10 06:19:23 EST
(In reply to Thomas Wolf from comment #2)
> See also bug 549869. It's not that simple.
That is the EGit case.

For m2e related issues (duplicate backends) see Bug 506676, Bug 569662, Bug 571577 and https://github.com/eclipse-m2e/m2e-core/issues/354
Comment 4 Jonah Graham CLA 2022-04-11 19:48:58 EDT
*** Bug 579655 has been marked as a duplicate of this bug. ***