Community
Participate
Working Groups
Created attachment 285689 [details] Screenshot of the Console view polluted with SLF4J warnings In the Eclipse IDE for Enterprise Java Developers 2021-03 M3 (containing m2e 1.17.1.20201207-1112), when running a Maven build (for example "Maven clean" for a minimal "pom.xml"), the Console view shows following SLF4J warnings at the beginning of the output in red (see attached screenshot): SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/C:/eclipse-jee-2021-03-M3/plugins/org.eclipse.m2e.maven.runtime.slf4j.simple_1.16.0.20200610-1735/jars/slf4j-simple-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [file:/C:/eclipse-jee-2021-03-M3/configuration/org.eclipse.osgi/6/0/.cp/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory] SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/C:/eclipse-jee-2021-03-M3/plugins/org.eclipse.m2e.maven.runtime.slf4j.simple_1.16.0.20200610-1735/jars/slf4j-simple-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [file:/C:/eclipse-jee-2021-03-M3/configuration/org.eclipse.osgi/6/0/.cp/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory] Uninstalling the following feature fixes the issue for me (no more SLF4J warnings): Name: m2e - slf4j over logback logging (Optional) Identifier: org.eclipse.m2e.logback.feature.feature.group Version: 1.17.0.20200924-1339 Provider: Eclipse.org - m2e
Eclipse m2e is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse-m2e/m2e-core/issues/ instead. If this issue is relevant to you, your action is required. 0. Verify this issue is still happening with latest Eclipse Platform and m2e release if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done if issue is still present when latest release: * Create a new issue at https://github.com/eclipse-m2e/m2e-core/issues/ ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience) ** In the GitHub description, start with a link to this bugzilla ticket ** Optionally add new content to the description if it can helps towards resolution ** Submit GitHub issue * Update bugzilla ticket ** Add to "See also" property (up right column) the link to the newly created GitHub issue ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>" ** Set status as CLOSED MOVED ** Submit All issues that remain open will be automatically closed next week or so. Then the m2e component for m2e will be made read-only.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
This issue is resolved by https://github.com/eclipse-m2e/m2e-core/pull/369
*** Bug 506676 has been marked as a duplicate of this bug. ***
