Logger in BEF is not working after initial Bazel builds start about bazel-eclipse HOT 3 CLOSED

I am also seeing this error on startup from the Gradle plugin only when the BEF is installed:

An internal error occurred during: "Loading available Gradle versions".
Class ch.qos.logback.classic.LoggerContext does not implement the requested interface org.slf4j.ILoggerFactory

from bazel-eclipse.

I suspect these issues happen when M2Eclipse is also installed. I see this at startup in my Eclipse that is affected when BEF is not installed:

org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
org.eclipse.m2e.logback.configuration: Logback config file: /Users/plaird/eclipse-workspace-2018-09b/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.9.1.20180912-1601.xml
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://517.fwk1850777594:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://517.fwk1850777594:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
org.eclipse.m2e.logback.configuration: Initializing logback

I have ripped out all external logging libs from BEF for the short term until we have time to investigate.
0da5faf

from bazel-eclipse.

This was resolved by doing what we can to log to the Eclipse platform logger, but we now have a /tmp/bef.log (on Unix) which is a log file fully under our control. We send all log lines there in addition to the platform logger.

from bazel-eclipse.