Yeah, that's exactly right. Glad to see that you got to the bottom of it. Apologies for not responding earler and saving you the trouble.
Originally Posted by jgaines
You can use a TEST.MF file in your project to describe your test-only dependencies. There's some more information about this in Christian's blog.
The one thing I'm still not sure about, though, is whether putting the test dependencies into the manifest with optional resolution is the smartest way to express them. If we used Maven, I could put 'em in the pom - but we don't.
What is the Best Way to capture test-only dependencies in an STS project?