Catching change dependencies on check-in or delivery
A user makes changes to 2 Eclipse projects, P, and D. Project P change depends on project D.
Later, user checks-in just the change for project P (forgetting that it depends on changes in project D).
Later, the user "delivers" to the main stream, after "catching up" the Repository Workspace to the main stream.
Other users who now check out the main stream get compile errors, because of the missing change set that wasn't yet created for project D.
Is there a way to have a process check to verify when checking in changes for project P that depend on changes in project D, that prevent this error (by requiring changes in D to be also checked-in?
One answer
Without a failing build, I'm not sure how you can be certain that one change will require another (it's not likely that every change will trigger a dependency issue). I think many teams address this by having a continuous integration build of the main stream (that would fail quickly in this case) and notify either the whole team or those who recently checked in changes of the problem. I don't think there is a built-in process check that could cover this sort of dependency.