RADE

Synopsis

adl_import object... [-from origin_ws_rev] [-tree local_tree] [-all_chg | {-chg chg...}] [-unco] [-import_proj | -import_merge] [-simul [-simul_dir temp_dir]] [-h|-help|-?] (1)
adl_import object... {-origin_path | -op} -from origin_ws_rev <...> (2)
adl_import -file file_name -from origin_ws_rev <...> (3)
adl_import -cs change_set... <...> (4)

Usage

This command allows the transfer of objects' changes (on components, directories, files) between two workspaces. Note that importing a change means doing it again inside the target workspace and not moving it (the changes remains valid in the origin workspace).
To import a whole workspace or several framework, you can run the [6] adl_import_ws command. 
You can launch this command in a graphic mode; see the [4] adl_gui command. To known the state of your workspace run the [5] adl_ds_ws command.

Here are presented three most frequent uses:

• Import from the absolute path of an object, in the origin workspace image (automatic search of the image and of the workspace, no need to mention them)

Example: adl_import <origin_image>/Fw1/Mod1.m/src/file1.cpp
Explanation: being in a given workspace, you can import a file seen in an image of another workspace, as soon as this image can be accessible on the local network.

• Import from the path of a current image object and a version of the origin workspace

Example: adl_import <current_working_image>/Fw1/Mod1.m/src/file1.cpp -from xxx
or:  cd <current_working_image>/Fw1/Mod1.m/src then adl_import file1.cpp -from xxx
Explanation: you give the name of a file being in the arrival workspace, and you want to import a version of this file, as it was in the given version of the origin workspace.

• Import a change set

Example: adl_import -cs ChangeSet1
Explanation: no origin workspace is needed. You give the name or identifier of one or several change set(s). Theses change sets contain somes changes in several workspace trees. The command try to import all of theses changes of all workspace trees in the destination workspace. If the related software objects are not in the destination workspace,  the command fails. You have to import the software objects before.

Workspace xxx revision
In the previous examples, xxx represents a revision of the origin workspace of the import.
In all the SCM commands accepting a workspace revision, the allowed syntaxes for specifying a revision are:  espace[.arborescence[.{numéro|label|last}]]

For the "chg" option, the specified changes can be the followings:

• del  Creation/deletion
• move  Move
• content Change of content (file element only)
• exec  Change of executable for Unix (file element only)
• descr  Change of description

If you use the -from option
The changes to import are read in the revision <origin_ws_rev> of the origin workspace.
  (1) The SCM object must be one of your current image.
  (2) The SCM object must be a relative path ("Fw1/Mod1.m/src/f1.cpp") or an identifier ("soid:xxx") to find in the origin workspace revision.
  (3) The file must contain relative paths or identifiers to find in the origin workspace revision.

If you don't use the -from option

Specify the SCM object you want to import as a path in the origin workspace's image.
The changes to import are read in the workspace revision which is projected in this image.
  (4) The change sets can be names or identifiers prefixed by "csid:".

NOTICE:

• If the object is a component or a directory, no contained object will be considered by the command.
• If the SCM object can be imported into several current workspace's trees, you must specify one with the option -tree.
• If the SCM object would be (seen as) deleted (for example by importing a move into a deleted folder)
• The command fails if any contained element is checked-out in the current image, if you don't use the option -unco.
• The command fails if any contained element is checked-out in another image of the current workspace.

[Top]

Naming Rules

Here are some samples of specifying a workspace revision:

[Top]

Options

adl_import accepts the following options:

[Top]

Examples

Import all the changes of FileName.txt from the revision projected in the origin image:

adl_ch_ws MyWsDev
adl_import <origin_ws_image_dir>/MyFw/FileName.txt

Import all the changes of FileName.txt from the PUBLIC revision of <origin_ws>:  

adl_ch_ws MyWsDev
adl_import <MyWsImageDir>/MyFw/FileName.txt -from <origin_ws

Import a ditto of FileName.txt:

adl_ch_ws MyWsDev
adl_import MyFw/FileName.txt -origin_path|-op -from <origin_ws>

Import a file "MyFile.c" from a non existing workspace "AnotherWs":  

adl_ch_ws MyWsDev
adl_import MyFw/MyFile.c -from AnotherWs
Looking for the workspace "AnotherWs"
#ERR# ADLCMD - 0421: No workspace "AnotherWs" found
Give an origin workspace revision with the format "ws[.tree[.{number|label|last}]".

##### THE COMMAND ENTIRELY OR PARTIALLY FAILED #####

Import a non existing file "MyWrongFile.c":

adl_ch_ws MyWsDev
adl_import MyFw/MyWrongFile.c
Verifying the path "MyWrongFile.c".
#ERR# ADLCMD - 7625: The path "MyWrongFile.c" belongs to the current image "image_MyWsDev".
If you don't use the option -from, the path must be found in the origin workspace's image.

##### THE COMMAND ENTIRELY OR PARTIALLY FAILED #####

Import change sets "MyChangeSet1" and "MyChangeSet2":

adl_ch_ws MyWsDev
adl_import -cs MyChangeSet1 MyChangeSet2

[Top]

References

[Top]

History

[Top]

Copyright © 2001, Dassault Systèmes. All rights reserved.