Is there a way in pants to forbid rather than excl...
# general
a
Is there a way in pants to forbid rather than exclude a dependency? I have a dep that, if it ships in a particular target, causes a production outage. I could exclude it, but that would cause import errors. Really, I want to raise a build-time error if someone has accidentally introduced a transitive dependency on that lib. Is this a plugin job?
c
it's not very user friendly yet.. so I'm expecting questions on how to apply it... suggestions for how to make it more approachable is welcome
a
🤔 I had seen that before but not really read it through. I'll take a closer look. When did that debut? I'm planning a 2.16 -> 2.19 migration in the next week or so.
Also, thank you, as always.
😄 1
c
There's even a example repo, cudos to @fresh-cat-90827 for that: https://github.com/pantsbuild/example-visibility to try this out more..
👀 1
I think it may have debuted in 2.16...
a
That's what i thought. Thanks!