search

tnozaki / cuelib

Automatically exported from code.google.com/p/cuelib
1 stars 2 forks source link

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

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
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 reported on code.google.com by monsterm...@gmail.com on 8 May 2008 at 9:28

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
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.

Original comment by monsterm...@gmail.com on 9 May 2008 at 7:56

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
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.

Original comment by monsterm...@gmail.com on 9 May 2008 at 11:40

GoogleCodeExporter commented 8 years ago 
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.

Original comment by monsterm...@gmail.com on 9 May 2008 at 11:55