Remove Conflicting Logging Dependencies and Use Spring Boot Logging Configuration #566
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Details
Description
Conflicting logging dependencies have been removed, and the logging configuration provided by Spring Boot is now relied upon. For more information about Spring Boot logging, refer to Spring Boot Logging.
Related Issue
No related GitHub issue.
Motivation and Context
Test failures were consistently observed in the CI pipeline after the fork was synced with the USDOT develop branch. Details of the test failures can be found here.
How Has This Been Tested?
All existing unit and integration tests were executed locally and confirmed to pass.
The services were started using Docker Compose, and the log output was verified to remain unchanged. Log excerpts have been attached for review.
Types of changes
Checklist:
ODE Contributing Guide