When MDR is used in the NetBeans IDE, it doesn't
matter very much how much output it prints to
System.out and System.err. However, it is a
problem for command-line tools that are embedding
MDR. In particular, if a tool wants to use both
System.err and System.out to output its own
messages, and _only_ its own messages, there is
currently no way to do it. And, MDR generates
enough messages where it becomes difficult for the
user to discern between MDR's informational,
internal messages, and user-level error messages
from my command-line application.

There are workaround available (in particular, use
System.setErr() and System.setOut() to redirect
all messages to some mechanism that ignores
everything println()'d and print()'d, and provides
other methods "realPrintErr()" and "realPrintOut"
that actually send the output to the console.
However, I don't think that will always be
reasonable for every user of MDR.

There is a org.netbeans.lib.jmi.util.Log class
that seems to be intended to be used as a logging
facility for MDR, that allows a developer to
choose where to output the messages. However, it
isn't part of the official published API, so I am
reluctant to use it. Also, there are a lot of
places in the MDR code that use System.xxx.out
directly, instead of using the Log class.

It would be nice if the logging facility worked on
a callback system, so that the MDR user could
supply a callback implementation that would log
the messages appropriately. In particular, I would
like to log all the MDR messages using the JDK 1.4
logging mechanism. That implies that MDR should
always supply the messages with some kind of
indicator about severity (informational, error,
warning, etc.). Then, a callback could translate
from MDR's severity indicators and generate the
appropriate log events for the logging API of
their choice.

If some facility is added to MDR's officual API,
then I can go through the MDR source code and do
the grunt work of converting all the users of
"System.xxx.out" to use the logging facility.