Skip to content

Replacing legacy logging by a SLF4J implementation #10

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

kuniss
Copy link
Member

@kuniss kuniss commented Jul 18, 2024

Solves GH issue #9.

Is based on branch pr-for-4.0-improvements%2Bxerces-removal for applying it on top of it.

Copy link

github-actions bot commented Jul 18, 2024

Test Results

147 tests   - 15   147 ✅  - 15   0s ⏱️ ±0s
 20 suites  -  2     0 💤 ± 0 
 20 files    -  2     0 ❌ ± 0 

Results for commit 8fec9a8. ± Comparison against base commit bc29edc.

♻️ This comment has been updated with latest results.

Allowing every application to be free which logging is used for
javapos-config-loader library.
which avoids an important message to be logged.
by eliminating version 2 API calls and replacing them accordingly by
calls from version 1.
This is for extending the range of applications compatible with the new
javapos-config-loader version as SLF4J version 2 can be used with
version 1 implementations too.
This introduces dependency to slf4j-api version 1.7.36.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant