c.c.logging just delegates to the underlying logging implementation.
If you haven't included a separate logging library on your classpath
(e.g., log4j) then it will default to using java.util.logging. Note
that by default the j.u.logging will output to stdout, and has a
default threshold of INFO. Since the spy macro outputs at debug, you
won't see it unless you change your configuration.
I'd recommend using log4j in preference to the default
java.util.logging. The following is a very basic configuration for
log4j; place it in a file called \"log4j.properties\" and place that
file (and the log4j JAR) on the classpath:
log4j.rootLogger=WARN, A1
log4j.logger.user=DEBUG
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%d %-5p %c: %m%n
The above will print messages to the console for :debug or higher if
one is in the 'user namespace, and :warn or higher in all other
namespaces.