SAP / SAP/cf-java-logging-support
Log4j2 config - packages property for plugins will be deprecated
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 82
- Forks
- 52
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 17
Description
Hello colleagues,
I just build in log4j2 with the exemplary config provided here:
https://github.com/SAP/cf-java-logging-support/blob/main/sample/src/main/resources/log4j2.xml
When running my tests so far, I receive a warning:
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
At the official page they mark it also as deprecated: https://logging.apache.org/log4j/2.x/manual/plugins.html
Not sure if you need to adapt the implementation of your actual plugins, but at least the configs needs to be adapted.
Kind regards
Hendrik
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 with sample/src/main/resources/log4j2.xml and compare its plugin configuration with the Log4j2 plugins documentation linked in the issue. Reproduce the warning while running the tests, then verify that the sample configuration no longer uses deprecated package scanning and the warning is gone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100