421 bumped to slf4j 2.0.1. About that time, they released 2.0.2. The changes are minor (currently up at https://www.slf4j.org/news.html) and don't affect us, but this helps us keep up.
While checking this, I noted a few places in the build where there were warnings about not having an implementation. Added a test logger to silence that.
Description
Updates version in managed dependencies, and adds dependency on test logger.
How Has This Been Tested?
Unit tests, and verified that viewer application produces log messages on known-noisy data.
Screenshots (if appropriate):
Types of changes
[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Motivation and Context
421 bumped to slf4j 2.0.1. About that time, they released 2.0.2. The changes are minor (currently up at https://www.slf4j.org/news.html) and don't affect us, but this helps us keep up.
While checking this, I noted a few places in the build where there were warnings about not having an implementation. Added a test logger to silence that.
Description
Updates version in managed dependencies, and adds dependency on test logger.
How Has This Been Tested?
Unit tests, and verified that viewer application produces log messages on known-noisy data.
Screenshots (if appropriate):
Types of changes
Checklist: