RADE

Source Code Manager

adl_force_so_chg

Setting software object changes

Quick Reference

Abstract

The adl_force_so_chg command sets software object changes as new current ones.

Synopsis
Usage
Options
Examples
References

Synopsis

adl_force_so_chg so_chg_id... -complete | -replace [-tree ws_tree_name] [-from_tree origin_ws_tree_name] [-simul [-simul_dir temp_dir]] [-h | -help | -?]
adl_force_so_chg -file file_path [-previous prev_file_path] -complete | -replace <...> [-already_imported imp_chg_file] [-simul [-simul_dir temp_dir]][-h | -help | -?]

Usage

This command imports the software object changes whose identifiers are passed to the command.

If the identifiers are given in the command line, you may prefix them with "chgid:" in order to avoid wrong line command interpretations.

If the option -complete is specified

For each change to import, the command looks for a matching current one, and it performs the same analysis than the collect or the synchronization (inclusion, merge...).

If the option -replace is specified

Each change becomes the new current one for the software object and the change type.
The previous software object changes are not considered: no merge with them is analyzed.
You can create merges to solve while passing more than one change for a software object and a change type. In that case, the projectable change is the first one of the group you pass.

TO BE USED ONLY in order to forget changes or in order to correct problems: the next propagations will apply the collect or synchronization rules; previous current changes might reappear or they might create merges to solve.

If the option -previous is specified

Only the changes read in <file_path> that are not found in <prev_file_path> are imported (delta). It's faster because most of the analysis is supposed to be done.

NOTICE that a previously imported change that has been forgotten won't be imported anymore.

All the identifiers are treated in a single transaction: you are able to consider software objects that were not visible from the current workspace.

The existing exclusivities are violated.

The command fails if any element is checked-out in any image of the workspace.

You have to refresh the images since one software object change is imported.

[Top]

Options

adl_force_so_chg accepts the following options:

`-h\|-help\|-?`	Help of the command
`so_chg_id`	Software object changes identifiers. You may prefix it with "chgid:"
`-complete`	The command consider the current changes.
`-replace <...>`	The changes to import become the new current ones, without considering the previous ones.
`-tree ws_tree_name`	The workspace tree in which the software object changes are to set as current ones.
`-from_tree origin_ws_tree_name`	Workspace tree from which are extracted the software object changes; used for the file contents server and the components responsible.
`-simul`	To simulate the import
`-simul_dir temp_dir`	Temporary directory path in which to project the files for simulation.
`-file file_path`	Path of the file containing the software object changes identifiers..
`-previous prev_file_path`	Path of the file containing software object changes previously imported.
`-already_imported imp_chg_file`	Path of the file in which will be written the changes identifiers that are already imported: it will be useless to treat them again (delta mechanism).

Examples

Changes the file with the "MyChgId" identification:

adl_force_so_chg -chgid MyChgId -complete

Changes the "MyFile" file replacing with "NewData":

adl_ch_ws MyWs
adl_force_so_chg -file Myfile -replace NewData

[Top]

References

[1]	adl_ls_so_chg: Listing software object changes

[Top]

History

Version: 1 [June 2001]

Document created

[Top]