I understand your concern in principle, and if this were a pants option, part of the "expected" pants interface, we would do a proper deprecation cycle. But it's just not practical to consider every JVM option that we technically allow a repo to set as something to undergo deprecation.