Determining dependent UCM activities in ClearCase

For any given element in an activity's change set, all versions are delivered from a given stream in the range between the version in the change set and either the version most recently delivered or the version in the stream's foundation baseline (whichever is later).




Notice that because version 3 of prog.c was delivered in a previous deliver operation, the dependencies between Activities B and C, which contain versions of prog.c, are as follows:

1. You can deliver Activity B without delivering Activity C.
2. To deliver Activity C, which contains version 6, users must also deliver Activity B, which contains the versions between 6 and the most recent delivery of prog.c.
3. Because Activity B also contains versions of lib.c, users may be required to deliver other activities to satisfy dependencies for lib.c.

For example, if Activity D (not shown in the above diagram) contained an undelivered version 6 of lib.c, delivering Activity B would require user to deliver Activity D as well.

For more information on delivering activities, refer to the Rational ClearCase Developing Software Guide.

With that said, a dependency between activities can arise from the fact that they contain versions of the same element, or because they are included in the same baseline.

There is no direct and reliable method to verify if an activity is required to be delivered with another due to a change set dependency.

The best way to determine if two activities need to be delivered together is to attempt a deliver of one activity by itself. If there are dependencies, a message will appear during the deliver notifying you of the dependency.