#22 Add a 'quiet' mode

[Wolfgang Kronberg]

Even when not using -verbose, ProGuard outputs a lot of
information to the console. This includes the banner
('Proguard, version ...') and information on reading
and writing files and directories. When using ProGuard
within makefiles, this is cluttering up the screen.

There should be a 'quiet' mode in which ProGuard does
not write anything to stdout/stderr unless a problem
occurs (problems should, of course, still be reported).

[Eric Lafortune]

Logged In: YES
user_id=555208

I'll consider it. I'm always hoping the information will
lead to more informative reports and questions from users as
well...

[Wolfgang Kronberg]

Logged In: YES
user_id=473935

Thank you for considering it! I also believe that the
information which you print out is valuable. It should stay
as it is as the default. I would just like to see an
additional switch which must be explicitly activated to turn
on the 'quiet' mode.

[claes]

I'm also interested in a quiet mode for easier detection of problems (warnings/notes) in the build process.

[Ville Oikarinen]

Optional further solutions:

1. When generating a dead code analysis, at least print a special line that indicates the start of the actual report. Then it will be easy to filter out lines before that marker line.
2. Print the diagnostic messages to stderr and the actual (dead code) analysis to stdout. This is standard behaviour in many applications and what stderr is meant for. This way it will be even easier to separate diagnostics from the report.

[Ville Oikarinen]

Ah, I just noticed that the dead code analysis can be redirected to a separate file in the proguard conf, by writing "-printusage file" instead of just "-printusage".