As of a few minutes ago, the testharness now depends on commons-logging
to build and run; it also takes advantage of log4j if it is there. See
you wont notice with ivy setting up the classpaths, but if you use the
IDE to build and run the tests/testharness, add commons-logging-1.0.4 to
the classpath of the testharness project, and, under idea, set up that
project to export commons logging to all its dependents.
right now the change doesnt do much; it just makes logging in the tests
at different levels a bit cleaner. All the test components now log via
sfLog() too. Anyone writing more tests (yes please!) should use the
commons-logging apis (subclasses of SmartFrogTestBase can call getLog()
to get a log), or, in the components, with sfLog().
Where this gets interesting is if I were to use smartfrog to host the
entire test run of tests itself. I havent done that yet, but I am
thinking about what it would take...
Registered Office: Cain Road, Bracknell, Berks RG12 1HN
Registered No: 690597 England