Show TOC

Using CVS as Development RepositoryLocate this document in the navigation structure

Use

You can use the SAP NetWeaver Developer Studio to integrate your development processes with the open-source version control system Concurrent Versioning System (CVS) and use it as your development repository. The development is almost identical from the point of view of development processes; in the end you are able to develop as normal, but the repository for the development sources and artifacts is CVS.

Prerequisites

You have installed the CVS repository.

You have configured the Developer Studio connection with the CVS repository.

Procedure

Setting up common development environment

  1. Set up and organize the sources in the version control system according to the recommended file system layout. For more information, see File System Layout .

  2. In the Developer Studio, open the Development Infrastructure perspective.

    To do that from the menu path, choose Start of the navigation path Windows Next navigation step Open Perspective  Next navigation step  Other....  End of the navigation pathChoose Development Infrastructure.

  3. Create a development configuration from scratch and specify the archive software components (SCs) that are used.

    For more information, see Managing Development Configurations .

  4. Create or specify the source SCs for development.

  5. Maintain usage relations and permissions (using the Access Control List (ACL) mechanism) between the source SCs.

  6. Create or submit the SC structure into CVS.

    Note that each SC root must be unique and that the nested SC path is not allowed.

  7. ( Optional ) Create or submit first DCs into CVS.

  8. Export the created development configuration as file.

    For more information, see Managing Development Configurations .

  9. Distribute the development configuration.

    Make the exported development configuration file available on a central place, for example a share. Each Developer Studio remembers the source location of each imported development configuration. If a new version is available, Developer Studio informs the user and provides an update possibility.

  10. ( Optional ) Submit the development configuration file into CVS.

Setting up local development environment

  1. Import the development configuration file from the share into the Developer Studio.

  2. Synchronize sources from CVS. Ensure that the root of the SC to which the synced DCs belong to is unique, and not nested.

    You can use CVS or use a standalone client or an Eclipse integration directly (dynamic mount option during checkout).

  3. Specify the local sync destination.

    Delete the project without content. We use Check out as project for source synchronization purpose only. The created project does not have a DC nature.

  4. Create DC projects in the Developer Studio.

    1. Open the Development Infrastructure perspective in the Developer Studio.

    2. Change the SC root accordingly, if necessary, in the Component Properties view.

      Refresh the SC. The synced DCs should be visible in the Component Browser view.

    3. Create a project on the DCs in the Component Browser view.

  5. Share the created DC projects with CVS.

Add the existing project(s) to CVS repository

For more information, see Adding Projects to the CVS Repository .

For the following types of DCs there are specifics when using the CVS as the repository. If you are using any of the listed DC types, you should consider concrete workarounds might be required for the normal development when using CVS as the repository: