Would the global verbose logging settings suffice here? I have a hard time drawing a line on which detailed logging bit gets it own flag. Since the need for detailed logging is hopefully limited to developers hacking or debugging a strange case, I lean towards a single verbose logging incantation turning it all on. The developer can handle all the noise.
Add --show-invalid-targets option
Review Request #1768 — Created Feb. 14, 2015 and discarded
|benjyw, jsirois, nhoward_tw, patricklaw|
This adds a global option to show the targets that are being invalidated in the build cache.
In order to get this working in tests, I had to figure out a way to keep this options check from
raising an exception from TestOptionValues(). To do this, I implemented
__contains__in both OptionValues and TestOptionValues.
Appends the target name to the console output when an invalid target is found as follows:$ PANTS_DEV=1 ./pants compile ./examples/src/java/com/pants/examples/protobuf/imports --show-invalid-targets ... 10:18:29 00:02 [protoc] Invalidated 1 target. examples/src/protobuf/com/pants/examples/imports:imports