PREDECESSORS / PRED
Use
A set of changes contained in an activity a2 can depend on a set of changes contained in another activity a1, which was integrated into the same workspace before a2 was integrated. The purpose of the predecessors command is to find such dependencies.
Versions are contained in different activities as follows:
● Activity a1 contains changes in the a.java file.
● Activity a2 (created after activity a1 was checked in) contains changes in files a.java and b.java.
The changes to file a.java in activity a2 depend on the changes made in this file in activity a1. Therefore, when activity a2 is to be integrated into another workspace, activity a1 also has to be integrated into this workspace in order to ensure a consistent state in the target workspace.
Syntax
Syntax |
PREDECESSORS <-a activityName> [-i isn] [-w sourceWorkspacePath] [-w targetWorkspacePath] [-m maxLevel] |
Arguments |
|
<-a activityName> |
Name of the activity whose predecessors have to be retrieved. |
[-i isn] |
ISN of the activity whose predecessors have to be retrieved. |
[-w sourceWorkspacePath] |
The source workspace path. If it is not specified then the current directory is used. |
[-w targetWorkspacePath] |
Specifies the workspace where the logical predecessors of the specified activities are located (target). If it is not specified then the current directory is used. |
[-m maxLevel] |
The level until which the search of predecessors has to be done. The default value is infinite. |
Description |
Displays a list of activities which are logical predecessors to the specified activities for a particular workspace but are not present in the target workspace.
If both the workspaces are specified as complete URL' in the format -w URL:http://... then no calls will be made to VFS and hence better performance can be expected when not used in shell mode. |
Example
Activity a10, integrated into the //test/dev workspace, needs to be integrated into workspace //test/cons.
To find all activities integrated into workspace //test/dev which have to be integrated into workspace //test/cons before activity a10 is integrated into this workspace, execute:
pred –a a10 –w //test/dev –w //test/cons