This message was deleted.

Maybe if you do it really dirty, like adding the other source sets classes directory to the class path via

buildscript

block and then using reflection it something like that. But I wouldn't recommend it, even if you get it working. If you go that route, also make sure to test whether it works after a fresh checkout. If you don't want to do it from another project, maybe you could consider from a different build, combining them using composite builds, it testing via TestKit.

In my expirence people tend to forget to run those tests. But you are right and it will be the best option. "cleanest" for sure

Yeah, that's what CI is for. 😄

😄