griffinbank / griffinbank/rules_clojure
Uses project's logging configuration for fetching dependencies
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 60
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
I'm not entirely sure how this is leaking, but fetching dependencies appears to be using the same logging config as the project has configured. If the project isn't appropriately configured, this can lead to emitting debug logs from eclipse, etc.
Instead, rules_clojure should have its own logging setup (probably slf4j-nop-based) and that shouldn't leak/interfere with the slf4j config of the project it's used with.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how rules_clojure configures logging while fetching dependencies and identify where the project's logging configuration is inherited. Confirm that dependency fetching uses an isolated, quiet logging setup and no longer emits or changes logs from the consuming project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100