Create an SLF4j provider implementation for the Equinox Log #740
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently when running an application with Equinox that uses other logging techniques one has some kind if mixture when it comes to logging as some parts are logging to Equinox Log (especially eclipse platform) and some are logging to something else (e.g. jul, log4j, ...).
A common approach for this is to use bridges that redirect different loggings to one api (e.g. slf4j) and then installing one desired provider to use that for unified logging.
To support such deployments, this now adds a slf4-provider that acts as such provider for slf4j so one can use it with slf4j api and also with such bridges to get a unified logging.