Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Documentation on Reasons Behind SLF4j Dependency Behavior #9

Open
romeara opened this issue Jan 5, 2016 · 0 comments
Open

Add Documentation on Reasons Behind SLF4j Dependency Behavior #9

romeara opened this issue Jan 5, 2016 · 0 comments

Comments

@romeara
Copy link
Member

romeara commented Jan 5, 2016

The releases of the SDK client jars only depend (at compile and runtime) on the SLF4j API, but no implementation. This is to prevent conflicts when the client is consumed with whatever the application consuming the library is using - this is a general practice for libraries which are not themselves a stand-alone application, but intended to be consumed by other applications.

We should add to the README.md file to better explain and clarify this choice

@romeara romeara self-assigned this Jan 13, 2016
romeara added a commit that referenced this issue Jan 22, 2016
…method

ISSUE #9 - Add an explanation of the SLF4j dependency pattern
@romeara romeara removed their assignment Feb 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant