Repository Path

Version 5 by Robin Shen
on Oct 15, 2011 12:31.

<< Changes from 4 to 5

compared with

Current by Robin Shen
on Oct 15, 2011 12:52.

Key

These lines were removed. This word was removed.

These lines were added. This word was added.

View page history

There are 5 changes. View first change.

		Repository path is used to refer to file in SCM systems. Example repository urls for different SCM systems:
		* Subversion: the path is relative to Subversion root, WITH a leading "/".
		{code}/my-app/trunk/pom.xml{code}
		Since this relatives to Subversion root, it will remain unchanged whether the checkout url defined in a Subversion repository is _svn://localhost/my-app_ or _svn://localhost/my-app/trunk_.
		Since the path is relative to Subversion root, above value will remain unchanged whether the checkout url defined in a Subversion repository is _svn://localhost/my-app_ or _svn://localhost/my-app/trunk_.

		* CVS: the path is relative to the CVS root, WITHOUT the leading "/"
		{code}my-app/trunk/pom.xml{code}
		Since this relatives to the CVS root, it will remain unchanged whether the checkout module defined in a CVS repository is _my-app_ or _my-app/trunk_
		Since the path is relative to the CVS root, above value will remain unchanged whether the checkout module defined in a CVS repository is _my-app_ or _my-app/trunk_

		* Perforce: the path should be an absolute path in the Perforce server, including the depot part
		{code}//depot1/my-app/trunk/pom.xml{code}

		* Visual SourceSafe: the path is an absolute path in sourcesafe database, starting with "$/"
		{code}$/my-app/trunk/pom.xml{code}
		Since this relatives to the sourcesafe root, it will remain unchanged whether the checkout project defined in a VSS repository is _$/my-app_ or _$/my-app/trunk_.
		Since the path is relative to the sourcesafe root, above value will remain unchanged whether the checkout project defined in a VSS repository is _$/my-app_ or _$/my-app/trunk_.

		* Accurev: the path is relative to the depot root, WITHOUT the leading "/"
		{code}my-app/trunk/pom.xml{code}

		* ClearCase: the path is an absolute path in ClearCase, including the vob part:
		{code}/vob1/my-app/trunk/pom.xml{code}

		* StarTeam: the path is relative to the view root, WITHOUT the leading "/"
		{code}my-app/trunk/pom.xml{code}
		Since this relatives to the view root, it will remain unchanged whether the source path defined in a StarTeam repository is _my-app_ or _my-app/trunk_
		Since the path is relative to the view root, above value will remain unchanged whether the source path defined in a StarTeam repository is _my-app_ or _my-app/trunk_

		* Git: the path is relative to git repository root, WITHOUT the leading "/"
		{code}my-app/trunk/pom.xml{code}

		* Mercurial: the path is relative to repository root, WITHOUT the leading "/"
		{code}my-app/trunk/pom.xml{code}

		* Bazaar: the path is relative to repository root, WITHOUT the leading "/"
		{code}my-app/trunk/pom.xml{code}

		* Team Foundation Server:
		* Team Foundation Server: this path is relative to the repository root, starting with "$/"
		{code}$/my-app/trunk/pom.xml{code}
		Since the path is relative to the repository root, above value will remain unchanged whether the source control folder defined in TFS repository is _$/my-app_ or _$/my-app/trunk_.