search

RomanHargrave / cuelib

GIT repo containing the currently (idle?) dead cuelib
GNU Lesser General Public License v2.1
0 stars 0 forks source link

TrackCutter should be able to print progress information to stderr #5

Closed RomanHargrave closed 9 years ago

RomanHargrave commented 9 years ago

From monsterm...@gmail.com on May 08, 2008 16:28:01

Currently, TrackCutter operates silently. It should be able to print progress information to stdout and/or stderr. This is particularly desirable when processing large numbers of files.

Ideally, both stdout and stderr should be supported. Messages to either channel should only be printed when this behaviour is activated via a command line option.

Original issue: http://code.google.com/p/cuelib/issues/detail?id=5

RomanHargrave commented 9 years ago

From monsterm...@gmail.com on May 09, 2008 12:56:56

After more consideration, it doesn't make much sense to send progress information to stdout. This is not functional data, but diagnostics, and diagnostics should go to stderr. If someone really wants it on stdout, they can use a shell redirect for that.

RomanHargrave commented 9 years ago

From monsterm...@gmail.com on May 09, 2008 16:40:23

This issue should be solved through the logging framework (see issue #7 ) for maximum flexibility.

Logging is normally configured outside of an application (specifically, through logging.properties). For convenience, we'll add some options that override the configured behaviour.

RomanHargrave commented 9 years ago

From monsterm...@gmail.com on May 09, 2008 16:55:36

Fixed in revision 44 .

Fixed issue #5 . TrackCutter now performs jdk 1.4 logging with INFO levels containing progress information. TrackCutterCommand now supports three settings that override jdk 1.4 logging settings for convenient configuration. Supported options are "none" (no cuelib logging), "specific (only TrackCutter logging), "all" (all cuelib logging). Logging overrides do not influence non-cuelib logging.

Status: Verified