BAH-4349 - Logging Configuration Fixes

[subhashydv]

JIRA → BAH-4349

Overview

This PR addresses logging configuration issues by resolving dependency conflicts and adjusting log levels for better visibility of application behavior.

Changes

1. Exclude Logback Dependencies to Avoid Conflicts

Added exclusions for logback-classic from multiple Spring and Liquibase dependencies to prevent conflicts with the Log4j2 logging framework currently in use:

• spring-boot-starter-data-jpa: Excluded logback-classic
• spring-boot-starter-actuator: Excluded logback-classic
• liquibase-core: Excluded logback-classic

Rationale: Spring Boot by default includes Logback as its logging implementation. Since this project uses Log4j2, excluding Logback prevents classpath conflicts and ensures consistent logging behavior throughout the application.

2. Enable INFO Log Level

Changed the root logger level from WARN to INFO:

Rationale: INFO level logging provides better visibility into application behavior, making it easier to troubleshoot issues and monitor application operations without overwhelming the logs with DEBUG-level details.

Impact

• Logging Framework: Ensures Log4j2 is the sole logging implementation, preventing conflicts
• Observability: Enhanced logging output for better debugging and monitoring
• Dependency Management: Cleaner dependency tree without conflicting logging implementations