explicitly provided dependencies between different...
# development
f
explicitly provided dependencies between different
java_library
targets that result in a cycle
w
yea. only file level dependencies are immune to cycles
inference should emit file-level dependencies for that reason
f
in same directory?
w
regardless of directory
f
well something to keep in mind for the dependency inference work
can you update the issue with the
only file level dependencies are immune to cycles
bit?
and
inference should emit file-level dependencies for that reason
w
done.
file level dependencies can also be used explicitly in BUILD files to get around this. but would recommend tackling inference before working on real world projects… will save you a lot of time i think.
f
I agree. I am triaging the current state of the JVM work on a real-world project (netty in this case) to learn what the current limits of the Pants plugin are.
so this issue points at dep inference being pretty important
w
yea. cycle tolerance was a blocker for
tailor
being useful in many real-world repos (it’s too fine grained otherwise)
but manually creating deps at that level is also a pain in the butt, and inference fixes that
f
which is why I’m stopping at providing anything more than deps on java_library targets
w
what do you mean
f
stopping using netty as a triage project since file-level deps are too annoying to provide by hand
w
got it