Community
Participate
Working Groups
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.
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?
See also bug 549869. It's not that simple.
(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
*** Bug 579655 has been marked as a duplicate of this bug. ***