Production error logging to System.out in IpcServer

Open Beginner friendly
#1,989 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
java
Domain
backend

Research direction

Start in maven-resolver-named-locks-ipc/src/main/java/org/eclipse/aether/named/ipc/IpcServer.java, focusing on debug() at line 184, info() at line 190, and error() at line 196. Replace the System.out and stack-trace output with SLF4J logging, then verify that all IPC server messages use the proper logging framework instead of standard output.

Written by the indexing model from the issue text.

Description

bug priority:major

Affected version: HEAD

File: maven-resolver-named-locks-ipc/src/main/java/org/eclipse/aether/named/ipc/IpcServer.java:196

private static void error(String msg, Throwable t) {
    System.out.println("[ipc] [error] " + msg);
    t.printStackTrace(System.out);
}

All errors in the IPC server go to stdout instead of a proper logging framework (SLF4J). In a production Maven build, these messages are invisible or interleaved with build output. Same issue for debug() (line 184) and info() (line 190) in the same file.

Originally reported in #1944.

Dominant language
Java
Stars
152
Forks
161
Avg merge
23h 25m
Merged PRs (30d)
48

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/maven-resolver

All issues in apache/maven-resolver

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.