Bug 579655 - Starting CDT generates SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"
Summary: Starting CDT generates SLF4J: Failed to load class "org.slf4j.impl.StaticLogg...
Status: CLOSED DUPLICATE of bug 578109
Alias: None
Product: CDT
Classification: Tools
Component: cdt-other (show other bugs)
Version: 10.6.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-10 23:01 EDT by Geoff Alexander CLA
Modified: 2022-04-11 19:48 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Geoff Alexander CLA 2022-04-10 23:01:40 EDT
I've found that starting CDT writes the following to stderr:

   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.

It doesn't seem cause any functional problem.  While this is only a minor problem when starting the Eclipse GUI, it does clutter the output when running the CDT command line formatter (https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2Ftasks%2Fcdt_t_format_app.htm) in a script.

I'm using CDT

   Version: 10.6.0.202203091838
   Build id: 20220309-1838

under

  Eclipse IDE for C/C++ Developers (includes Incubating components)
  Version: 2022-03 (4.23.0)
  Build id: 20220310-1457
  OS: Linux, v.5.3.18-150300.59.60-preempt, x86_64 / gtk 3.24.20
  Java vendor: Eclipse Adoptium
  Java runtime version: 17.0.2+8
  Java version: 17.0.2

on openSUSE Leap 15.3.
Comment 1 Jonah Graham CLA 2022-04-11 19:48:58 EDT
Thanks Geoff for the report. This has been an issue in Eclipse for a long time and it seems there is no consensus on the correct way to resolve the issue. I don't believe the problem originates with CDT and marking this as a duplicate of Bug 578109.

*** This bug has been marked as a duplicate of bug 578109 ***