I think that thare are many types of changes for which I'd advise full builds prior to commit. Off the top of my head, here are a few more cases that I've run into:
There are *PLENTY* of cases. I debating brainstorming a more complete list, but thought my email was long enough already. :)
- Just because an API isn't public, doesn't mean that other parts of the JDK don't depend on its presence or precise semantics.
Deploy used to break quite a bit due to sun.* changes. That's why gatekeepers really need to build most of the gates, at least as far as images.
I'd say that these cases are rare, but I'm sure any gatekeeper ("integrator" if you're using the old terminology) will appreciate if a full build was done at some point prior to commit.
Agreed, I'm happy to give the "noose" [1] for extra-careless acts. Extra points if you identify the office who last received it. ;) Brad [1] http://blogs.sun.com/wetmore/resource/images/PowerNoose.JPG