RADE

Source Code Manager

adl_attach_is

Attaching components in remote workspace

Quick Reference

Abstract

The adl_attach_is command is an intersite command that is used in the process of setting up an intersite transfer between the current workspace and a workspace of another SCM site.

Synopsis
Usage
Options
Examples
References

Synopsis

adl_attach_is component... [-transfer transfer_name] [-tree ws_tree_name] [-h | -help | -?]
adl_attach_is framework...[-transfer transfer_name] [-mod] [-tree ws_tree_name]
adl_attach_is -attached_fw_mod [-transfer transfer_name] [-tree ws_tree_name]

Usage

The adl_attach_is command is used after having declared [1] an intersite transfer between a local workspace and another workspace of another remote site. It is used to attach components in both the remote mirror workspace and the current workspace.

The command operates on both the current workspace and the remote mirror workspace: the components are attached in the remote mirror workspace and then an intersite transfer is launched for transferring the new components into the current workspace.

adl_attach_is provides the same options as the adl_attach command, but the main usage will be to provide a list of frameworks to attach, and, as the command is built upon the general intersite command adl_site_transfer [2], all internal modules will be attached during the transfer from the remote site to the local site. It is possible to attach several components belonging to different trees, in the case of multi-tree intersite transfers. Each component is attached in the mirror workspace, then locally transferred, before another component is taken in account.

The components to be attached must be accessible in the parent workspace (see the adl_ls_fw_is [3] command with the -all option to list the accessible frameworks). The current workspace must be synchronized with the remote parent workspace in case the components to attach appeared in it since the last synchronization.

If there is a current image, all the files and directories belonging to the new component(s) will be projected in it at the end of the command. If the current workspace has several images, the others will have to be refreshed using the adl_refresh [4] command.

[Top]

Options

adl_attach_is 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
-transfer transfer_name	Name of an existing transfer of the current workspace.
`-mod`	Attach all internal modules and data components in the workspace hierarchy for the given frameworks
`-attached_fw_mod`	Attach all internal 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]

Examples

Attachment of the “MyFramework” framework in the current workspace where a transfer named "Transfer1" has been set up with a remote workspace where this framework is currently managed.

adl_attach_is MyFramework -transfer Transfer1
...

Attachment of the modules of the “MyFramework” framework, not yet in the "MyWsDev" workspace:

adl_ch_ws MyWsDev
adl_attach_is MyFramework -mod -transfer Transfer1

Having a transfer set up between several workspace trees of the current workspace, attachment of the “MyFramework” framework in the tree ToolsTree:

adl_attach_is MyFramework -tree ToolsTree -transfer Transfer1

[Top]

References

[1]	adl_mk_is_transfer: Creating an intersite transfer
[2]	Inter site transfer: Sharing components between SCM sites
[3]	adl_ls_fw_is: Listing framework in remote mirror workspace
[4]	adl_refresh: Refreshing a workspace image

[Top]

History

Version: 1 [Mar 2002]

Document created

[Top]