ah.. I think this might be the problem where our maven setup is screwy. You need to build the test jar perhaps.
then try to build everything again. Just a thought. John Sanda knows more about that test-utils and the way it interacts with the rest of the build. Maybe he can chime in. Usually the problem happens when you use -Dmaven.test.skip. We have been using -DskipTests to help avoid this kind of problem. Maybe that's something you should try. If you are using -Dmaven.test.skip, try using -DskipTests instead. I think there is a thread on that somewhere.