Problem
20+ production source files use System.out.println() / System.err.println() instead of proper logging framework.
Impact
- Severity: MEDIUM
- Category: Production Readiness
- Cannot control log levels in production
- No structured logging
- Poor observability
- Cannot integrate with centralized logging
Affected Files
./jplatform-api/src/main/java/org/flossware/jplatform/api/*.java (multiple)
./jplatform-launcher/src/main/java/org/flossware/jplatform/launcher/PlatformLauncher.java
./jplatform-terminal-ui/src/main/java/org/flossware/jplatform/terminal/TerminalConsole.java
./jplatform-monitoring/src/main/java/org/flossware/jplatform/monitoring/ApplicationResourceMonitor.java
... and 17 more files
Required Action
Replace all System.out.println() with logger.info() / logger.debug():
Before:
System.out.println("Starting application: " + appId);
After:
private static final Logger logger = LoggerFactory.getLogger(MyClass.class);
// ...
logger.info("Starting application: {}", appId);
Priority
P1 - High - Should be fixed before production deployment.
Detection
find . -name "*.java" -path "*/src/main/*" | xargs grep -l "System\\.out\\|System\\.err"
Problem
20+ production source files use
System.out.println()/System.err.println()instead of proper logging framework.Impact
Affected Files
Required Action
Replace all
System.out.println()withlogger.info()/logger.debug():Before:
After:
Priority
P1 - High - Should be fixed before production deployment.
Detection