if

Goal

is an Optionable, then perhaps not

great question

one way to test this would be to run something with

--loop

and see whether changing an option causes invalidation

but that could be done like by changing pants.ini? that sounds iffy

unclear

figuring out what contributes to the hash of the goal’s Options class sounds like a good way to investigate

and "fingerprinting" as we think about it in v1 only occurs in v2 on an ExecuteProcessRequest basis, in that we have a cache for those.