cqframework / cqframework/cqf-tooling
Remove log4j dependencies
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 22
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
The cqf-tooling currently includes both slf4j and log4j as non-optional dependencies. This means downstream projects are required to exclude the dependencies manually, like shown here:
https://github.com/DBCG/cqf-ruler/blob/master/pom.xml#L111
To Reproduce
Steps to reproduce the behavior:
See pom
Expected behavior
The logging in the tooling should depend only on the slf4j API, with an implementation of that API being marked as optional (the cqf-ruler uses logback, for reference)
Contributor guide
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 inspecting the cqf-tooling pom and compare its logging dependencies with the referenced cqf-ruler pom. Verify the dependency tree and project build after the change; done means downstream users can rely on the slf4j API without receiving log4j as a required dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100