CLI outputs could be done directly to terminal instead of writing to dbptk-app.log.txt

[pandabear]

Description:

I tried using master-branch built dbptk.

The usage of CLI tool produces dbptk-app.log.txt whenever it is being invoked. I feel that this is not necessary, because on terminal or command prompt, we can utilize redirections. The old behaviour can still be invoked with java -jar dbptk-app-2.11.0-SNAPSHOT.jar &>> dbptk-app.log.txt.

The benefit this change brings, I believe, is that it'll give more control to the cli-tool user to manage and control the log file outputs via familiar tools of bash redirection and logrotate. At the same time this eliminates how the current log file feels being forced upon usage even when command is run out of curiosity.

[dosubot]

Hi, @pandabear. I'm Dosu, and I'm helping the keeps/dbptk-developer team manage their backlog and am marking this issue as stale.

Issue Summary

• You proposed that the CLI tool should output logs directly to the terminal by default instead of always writing to dbptk-app.log.txt.
• This change would allow users to manage logs with standard shell redirection and avoid unwanted log file creation during casual use.
• The current behavior could still be preserved through explicit redirection if desired.
• There has been no further activity or comments on this issue since it was opened.

Next Steps

• Please let me know if this issue is still relevant to the latest version of the keeps/dbptk-developer repository by commenting here.
• If I do not hear from you within 7 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

[junafan9000]

Hello! On behalf of @pandabear, I can say the issue is still relevant!