Is it good to set System.out.println in a separate method?

Question

I work with a piece of code that seems strange to me. The code I'm working on is part of an import utility that takes a CSV file and imports data into a database.

Inside the code, I see:

ImportUtils.printf("Validation started");

When I look at this method, it just calls System.out.println:

public static void printf(String s) {
    System.out.println(s);
}

Are there any advantages to this? Could this pose a problem in the future?

Answer 1

System.out.println API . ( , Log4j, SLF4J ). , . , , ... (, ), , .

Answer 2

. , , , System.out - , System.setOut(). , .

Answer 3

, - , ImportUtils.printf.

? , , .

Answer 4

printf , printf , printf .

, , . printf.

Answer 5

Java, " Fortran ", C.

, , - C- API. "DisplayText" - , , .

Answer 6

, - - .

, system.out. , . , , . , . ..

. , system.out. - , .