Task 2.4: Migrate SLF4J Dependencies

Task Description

Replace dot.slf4j-api and dot.slf4j-jcl with standard SLF4J dependencies

Status: 🔄 PENDING

Scope

• Verify current SLF4J usage patterns in codebase
• Remove dot.slf4j-api and dot.slf4j-jcl from POM files
• Ensure standard SLF4J from logging BOM is used
• Test logging functionality across application

Implementation Plan

1. Analysis Phase:

   • Review current SLF4J usage patterns
   • Identify any custom SLF4J configurations
   • Verify logging BOM already includes standard SLF4J

2. Dependency Update:

   • Remove com.dotcms.lib:dot.slf4j-api from BOM and dotCMS POM
   • Remove com.dotcms.lib:dot.slf4j-jcl from BOM and dotCMS POM
   • Confirm standard SLF4J from logging BOM is properly inherited

3. Code Migration:

   • Find any repackaged SLF4J imports (if any)
   • Replace with standard SLF4J imports
   • Verify logger initialization patterns

4. Testing:

   • Test logging functionality across application
   • Verify log levels work correctly
   • Check log appenders and configurations

Acceptance Criteria

• [ ] Current SLF4J usage patterns documented
• [ ] Repackaged SLF4J dependencies removed from POM files
• [ ] Standard SLF4J from logging BOM confirmed active
• [ ] All logging functionality works correctly
• [ ] No changes to log levels or output format
• [ ] Integration tests pass with proper logging

Claude Assistance Benefits

• Usage Analysis: Claude can analyze SLF4J usage patterns across codebase
• Import Updates: Handle any necessary import statement changes
• Configuration Review: Help review logging configurations
• Testing Support: Identify logging test cases that need verification

Related

• Epic: #32675 - Remove Repackaged Dependencies
• Phase: 2 - Low-Risk Migrations
• Priority: Medium
• Estimated Effort: 1 day (with Claude assistance)

Technical Notes

• SLF4J is used for logging abstraction
• Standard SLF4J may already be available via logging BOM
• Verify no breaking changes in logging behavior
• Check for any custom SLF4J bridges or adapters

Start by locating the BOM and dotCMS POM files containing com.dotcms.lib:dot.slf4j-api and com.dotcms.lib:dot.slf4j-jcl, then review SLF4J imports and logging configurations. Run the relevant integration tests and verify that standard SLF4J is inherited from the logging BOM, logging behavior and output remain unchanged, and all tests pass.