Using the RAM2SVN Plug-in

RAM2SVN integrates RAM with Subversion Version Control in much the same way as the RAM CVS integration. When an artifact is submitted to RAM information about its location in SVN is recorded. This means that subsequent imports of that asset into users workspaces allows the contents of the asset to be fetched from Subversion.

Submitting assets into RAM and Subversion

To submit an existing project (already under Subversion control) to RAM you complete the following steps:

1. Right click the project and select New > Other > Asset.

2. Complete the details about the asset including giving it a name and a version.
3. In the Contents tab of the asset details, select the projects and files you wish to include in the asset.

4. Click Submit to submit the new asset to RAM, presuming that you have an existing connection to a RAM server.

5. Complete the submit process by clicking OK.

Importing assets to the local workspace

Assets that have Subversion information can be imported either from RAM or from Subversion (SCM - Source Code Managment). To import from Subversion complete the following steps:

1. Identify the asset you would like to import and select Import.

2. When prompted select Import files through SCM.

3. You can choose to:

   • Import latest from current branch   will import the HEAD version of the location used when the asset was initially created.

   • Import from other existing branches   will import the asset from the HEAD version of another branch. The list of available branches are described by Subclipse using the subclipse:tag property set on the top directory of the project.

   • Import by creating a new branch   will create a new Subversion branch which will then automatically check out to your workspace. You will need to enter a location for the new branch. This location is relative to the repository root e.g. branches/new_branch.

4. Click Next.

5. Click Finish. Presuming the client has a connection to the Subversion repository the asset will be fetched to your local workspace ready for editing.

6. To submit your changes to the asset simply commit them in the usual way using the Subclipse plug-in.

Known Problems

• there are no known problems at the moment

FAQ

• Who is the RAM2SVN plugin designed for?
  • Managers managing projects which are under Subversion control, and want to have an asset with those projects in Rational Asset Managment
• What should I do, to import a project (which is under Subversion Control) from RAM, which is not the latest version?
  • Choose do not import through SCM option when importing project
• How can I check when my license will expire?
  • Check the expiry date in the RAM2SVN.properties file in Eclipse Directory\plugins\com.clearvision_cm.ram2svn directory
• What will happend if I will submit an asset with source under Subversion control?
  • Asset will be submitted, and all source under Subversion control will be updated in subversion too
• Is the asset file also under Subversion control (when submitting via RAM2SVN plugin)
  • "Yes" if it contains any source under Subversion control, otherwise "No"
• Does the RAM2SVN plugin store user authentication information e.g. Subversion or RAM user name or password?
  • No
• Who should I contact in case of any errors

  • support@clearvision-cm.com