that's actually where I'm feeling it's awkward right now, is test support code. Currently, I'm creating another top-level project with test utils in it, and it just feels wrong

psfried: another approach is to where test-support code gets published in a

-tests.jar

, and then other dependencies have a

test

-scoped dependency on the

-tests

classifier of the library whose test utilities they want to use (just drive-by $0.02)