Getting Started › Detached Development - Working Offline

Detached Development - Working Offline

The CA Harvest SCM Plug-In for Eclipse supports detached development. Detached development lets you disconnect a project from the CA Harvest SCM repository and thereafter work offline on resources in this project without interacting with the CA Harvest SCM repository. Reconnecting the project after working in a disconnected state lets you synchronize your offline changes to the CA Harvest SCM repository.

The following restrictions apply to detached development and working offline:

• A project can only be connected or disconnected if it has already been synchronized with the CA Harvest SCM repository.
• Detached development in the CA Harvest SCM Plug-In for Eclipse does not support a lost network session. If you either purposely or accidentally disconnect the network cable during an active CA Harvest SCM session, you must connect the network cable, shut down the CA Harvest SCM Plug-In for Eclipse, and then restart it to initiate a new session.

To use detached development or work offline

1. Disconnect your project from CA Harvest SCM:
   • To disconnect a single project, right-click the project and click Team, Disconnect Project.
   • To disconnect all projects in your workspace, click CA Harvest SCM, Disconnect All Projects.

   The project-level folder shows the text "OFFLINE," and symbols and icons indicate resource status.

2. You can work on files that have or have not been checked out of CA Harvest SCM.

   When a project is disconnected from the CA Harvest SCM repository, all Eclipse functions that require an CA Harvest SCM connection are disabled.

3. After you finish making changes, reconnect the current project or all projects in the workspace:
   • To reconnect a single project, right-click your project and click Team, Reconnect Project.
   • To reconnect all projects, click CA Harvest SCM, Reconnect All Projects.

   Note: The reconnect menu options are available only if a project is in detached or offline mode.

   The project-level folder shows the CA Harvest SCM broker name and project name when a project is connected.

4. Apply your changes to CA Harvest SCM by right-clicking the project and clicking Team, Synchronize with CA Harvest SCM.

   Every modified or new file in the project is marked as an outgoing change.

5. Right-click the project in the Synchronizer view and select Commit to Repository to apply the changes.

   Every file that was modified or that is new is checked in.