RADE |
Source Code Manager |
adl_attachAttaching components |
| Quick Reference | ||
AbstractThe adl_attach command attaches, in a workspace, components seen by parent workspaces. |
adl_attach component... [-tree ws_tree_name] [-h | -help | -?]
(1)
adl_attach framework...[-mod] [-tree ws_tree_name] (2)
adl_attach -attached_fw_mod [-tree ws_tree_name] (3)
adl_attach attaches a framework or a module or a data module to the current workspace. The attachment is mandatory prior to modify existing framework, module or data module. A logic link is created between the files managed by the file system and the files managed in the SCM database.
adl_attach projects directories and files from the database into the file system. By default, the modules are not projected; use the -mod option to project the modules.
(1) If the component you want to attach is either a module or a data
component, its framework must be already attached.
If the component you want to attach is a framework, and if any have been found in more
than one workspace tree of the current workspace, you have to choose a workspace tree.
(2) If you use the option -mod and frameworks are specified, all their
modules and their data components will be attached.
(3) If you use the option -attached_fw_mod, all modules and all data
components belonging to the attached frameworks will be attached.
The framework, module or data must not be already attached. They must be accessible in the parent workspace (see the adl_ls_fw [2] command with the -all option to list the accessible frameworks). The current workspace must be synchronized with its parent.
After an attachment, adl_ds_ws command will indicate Promotion: to do. At this moment there is nothing to promote but SCM considers an attachment as a modification.
The command works without having a current working image. If there is one current image, the attachment is followed by a refresh in order to project all the files and directories belonging to the new component(s).
Last, if there are other images, you have to make a "Refresh" on each of them using the [4] adl_refresh command
[Top]
adl_attach accepts the following options:
| -h|-help|-? | Help of the command |
| component... | Path(es) of the components to attach |
| framework | Name of the framework to attach |
| -mod | Attach all contained modules and data components in the workspace hierarchy |
| -attached_fw_mod | Attach all contained modules and data components in the workspace hierarchy of attached frameworks |
| -tree ws_tree_name | Name of the workspace tree in which the framework(s) will be attached |
[Top]
Attach of the “MyFramework” framework only:
adl_attach MyFramework |
Attach of the “MyFramework” framework and of all its modules and data:
adl_attach MyFramework -mod |
Attach of the modules of the “MyFramework” framework, not yet in the "MyWsDev" workspace:
adl_ch_ws MyWsDev |
Attach of the “MyFramework” framework in the tree ToolsTree:
adl_attach MyFramework -tree ToolsTree |
Attach all contained modules and data components in the workspace hierarchy of attached frameworks:
adl_attach -attached_fw_mod |
[Top]
| [1] [2] [3] [4] |
adl_ch_ws: Changing workspace adl_ls_fw: Listing frameworks adl_photo: Freezing your workspace adl_refresh: Refreshing your workspace |
[Top]
| Version: 1 [Feb 2001] | Document created |
[Top]
Copyright © 2001, Dassault Systèmes. All rights reserved.