You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: