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

Investigate strategies to get around client logging issues wrt the log4j dependency of Uzaygezen #2104

Open
lossyrob opened this issue Mar 28, 2017 · 0 comments
Labels
technical debt https://en.wikipedia.org/wiki/Technical_debt

Comments

@lossyrob
Copy link
Member

Uzaygezen (which is a dependency of geotrellis-spark, as seen here) depends on log4j directly, instead of depending on the slf4j logging interface and allowing users to bring in the logger of their choice.

This doesn't play nice with client applications that bring in geotrellis-spark, but want to use something like logback-classic to do their logging.

This issue is about investigating ways to get around this issue, either by excluding that dependency in a way that it will not be included as a transitive dependency to geotrellis-spark, or some other method.

@lossyrob lossyrob added this to the 1.2 milestone Mar 28, 2017
@echeipesh echeipesh modified the milestones: 2.0, 1.2 Sep 7, 2017
@echeipesh echeipesh removed this from the 2.0 milestone Aug 10, 2018
@pomadchin pomadchin added the technical debt https://en.wikipedia.org/wiki/Technical_debt label Jul 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
technical debt https://en.wikipedia.org/wiki/Technical_debt
Projects
None yet
Development

No branches or pull requests

3 participants