what's the best pattern for avoiding accidental dependencies on test code from production code? Right now I have a single lockfile for all my code, but it includes things like

hamcrest

. I get that the dependency won't be packaged when I wrap up my production code, but it feels like it's very easy for me to accidentally introduce dependencies on the "wrong" things in prod code. The obvious idiom seems to be that I would create a second resolve and move the test stuff there, but then I suddenly have to parametrise lots and lots of things because I need production code to be usable in both resolves and test-only dependencies need to become more verbose too. Is there perhaps a way to "layer" resolves so that my test one "extends from" my production one, and pick different resolves by default for prod vs test?

I think you may want to look into https://www.pantsbuild.org/v2.16/docs/validating-dependencies

thanks, I'll take a look at that!

No, but the alpha is available so feel free to try it out and give feedback!