Is there a testing framework that would prevent me...
# community-support
e
Is there a testing framework that would prevent me from adding a dependency on a specific project from a specific set of my projects?
e
e
I was thinking of something more Gradle specific, but I guess a convention plugin would be my best bet.
t
Yeah convention plugin is probably my first tool to grab. Probably a few ways you could go about it. task that finalizes your compile task and makes assertions about the contents of the configuration or something like that. being its own task would let you put all kinds of info in the error you throw to explain what/why/how to fix at a high level in build log
otherwise you could hook into some part of your test runtime and look at the classpath to make assertions about what is on it. if the issue is in dependency config I thing doing it as close to that as possible would be the best way