Skip to content

[P1] Replace System.out/System.err with proper logging (SLF4J) #307

@sfloess

Description

@sfloess

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"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions