Java2D currently has trace methods (J2dTrace*) that work only on debug
builds. We would also like the ability to have trace output in release builds.
For example, we may want to ask users what kinds of system info our
libraries are detecting, which we could retrieve through such a system
(printing out the initialization information to the command shell).

We need to add equivalent trace statements that are enabled in all builds,
not just debug builds; these statements will work exactly like the J2dTrace*
methods, so the semantics for using the trace statements is the same.

Note: We need to keep in mind that these methods are compiled in always,
thus we need to avoid putting trace calls in any performance-sensitive areas.
We anticipate putting these trace calls only in places that are called
infrequently (such as an init routine at startup) or in problem situations
where we might like to know the errors that the system is seeing.

###@###.### 2005-06-09 23:03:41 GMT