Updated Branches: refs/heads/master 56ee603d2 -> cb24f99ed
general formatting Project: http://git-wip-us.apache.org/repos/asf/maven-scm/repo Commit: http://git-wip-us.apache.org/repos/asf/maven-scm/commit/cb24f99e Tree: http://git-wip-us.apache.org/repos/asf/maven-scm/tree/cb24f99e Diff: http://git-wip-us.apache.org/repos/asf/maven-scm/diff/cb24f99e Branch: refs/heads/master Commit: cb24f99ed25ff81ea1ea1ad1042b1fe0175cba0e Parents: 56ee603 Author: Hervé Boutemy <hbout...@apache.org> Authored: Sun Oct 27 16:01:00 2013 +0100 Committer: Hervé Boutemy <hbout...@apache.org> Committed: Sun Oct 27 16:01:00 2013 +0100 ---------------------------------------------------------------------- src/site/apt/accurev.apt | 6 +- src/site/apt/bazaar.apt | 8 +-- src/site/apt/clearcase.apt | 20 +++---- src/site/apt/cvs.apt | 30 +++++----- src/site/apt/git.apt | 10 ++-- src/site/apt/jazz.apt | 124 +++++++++++++++++++-------------------- src/site/apt/local.apt | 4 +- src/site/apt/mercurial.apt | 4 +- src/site/apt/perforce.apt | 4 +- src/site/apt/starteam.apt | 4 +- src/site/apt/subversion.apt | 4 +- src/site/apt/synergy.apt | 4 +- src/site/apt/tfs.apt | 6 +- src/site/apt/vss.apt | 12 ++-- 14 files changed, 120 insertions(+), 120 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/accurev.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/accurev.apt b/src/site/apt/accurev.apt index 0275734..68465ed 100644 --- a/src/site/apt/accurev.apt +++ b/src/site/apt/accurev.apt @@ -30,12 +30,12 @@ SCM Implementation: Accurev * General Info - Link : {{http://www.accurev.com//}} + Link: {{http://www.accurev.com//}} - License : Commercial + License: Commercial * SCM Url ------- scm:accurev:server:port/depot/my_app/ -------- \ No newline at end of file +------- http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/bazaar.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/bazaar.apt b/src/site/apt/bazaar.apt index 2994ae5..fb2e285 100644 --- a/src/site/apt/bazaar.apt +++ b/src/site/apt/bazaar.apt @@ -1,7 +1,7 @@ ------ SCM Implementation: Bazaar ------ - Torbj�rn Eikli Sm�rgrav + Torbjørn Eikli Smørgrav ------ 2006-02-01 ------ @@ -30,9 +30,9 @@ SCM Implementation: Bazaar * General Info - Link : {{http://bazaar-vcs.org/}} + Link: {{http://bazaar-vcs.org/}} - License : GNU General Public License + License: GNU General Public License "Bazaar-NG is a decentralized revision control system designed to be easy for developers and end users alike. Decentralized revision control systems give people the ability to work @@ -55,7 +55,7 @@ scm:bazaar:url_to_repository ------- scm:bazaar:http://host/v3 (read only) -scm:bazaar:sftp://username:password@host/~/dev/project/v3 (relativ path) +scm:bazaar:sftp://username:password@host/~/dev/project/v3 (relative path) scm:bazaar:sftp://host:port/home/smorgrav/dev/project/v3 (absolute path without explicit username) scm:bazaar:file://C:/dev/project/v3 (windows drive) scm:bazaar:file:///home/smorgrav/dev/project/v3 (linux drive) http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/clearcase.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/clearcase.apt b/src/site/apt/clearcase.apt index c5ad855..2ae40e4 100644 --- a/src/site/apt/clearcase.apt +++ b/src/site/apt/clearcase.apt @@ -98,8 +98,8 @@ load /myvob/modules/my_module Notice that checking out from a tag (which is used by the maven-release-plugin) is currently not supported for user-supplied config specs. Another point to remember is that ClearCase does not check out projects directly into the checkout directory, but instead a sub-directory - of the checkout directory (e.g. /checkoutdir/myvob/modules/my_module instead of just /checkoutdir). This is unexpected by the - scm:bootstrap command, Continuum, + of the checkout directory (e.g. <<</checkoutdir/myvob/modules/my_module>>> instead of just <<</checkoutdir>>>). This is unexpected by the + <<<scm:bootstrap>>> command, Continuum, the Maven-Release-Plugin and other users of the ClearCase SCM provider. Adjust the build working directory after the checkout (in Continuum, for example, by adjusting the POM file location within the Build definition). @@ -135,7 +135,7 @@ load <load_directory> ------- Notice that ClearCase does not check out projects directly into the checkout directory, but instead a sub-directory - of the checkout directory (e.g. /checkoutdir/myvob/modules/my_module instead of just /checkoutdir). When using auto-generated + of the checkout directory (e.g. <<</checkoutdir/myvob/modules/my_module>>> instead of just <<</checkoutdir>>>). When using auto-generated config specs, the correct location of the project directory is provided to other modules that use the ClearCase SCM provider, such as the scm:bootstrap command. As a consequence, the build can automatically be run from the correct working directory. @@ -170,9 +170,9 @@ cleartool: Error: A registry entry already exists for "johndoe-mymachine-maven-m ** -vws parameter on mkview command - By default, when creating a view, the -vws parameter of the mkview command is used to specify the location of the view store. - In many environments, however, the -vws parameter can be omitted, and ClearCase uses appropriate defaults. - To turn off the usage of the -vws parameter, configure it in the clearcase-settings.xml file: + By default, when creating a view, the <<<-vws>>> parameter of the <<<mkview>>> command is used to specify the location of the view store. + In many environments, however, the <<<-vws>>> parameter can be omitted, and ClearCase uses appropriate defaults. + To turn off the usage of the <<<-vws>>> parameter, configure it in the <<<clearcase-settings.xml>>> file: ------- <clearcase-settings> @@ -182,8 +182,8 @@ cleartool: Error: A registry entry already exists for "johndoe-mymachine-maven-m ** Viewstore location - This setting is only relevant if and when <<useVWSParameter>> has been left or set to the default value of <<true>>. - By default the viewstore location <<\\\\$\{hostname}\viewstore>> is used. To define another viewstore location, + This setting is only relevant if and when <<<useVWSParameter>>> has been left or set to the default value of <<<true>>>. + By default the viewstore location <<<\\\\$\{hostname}\viewstore>>> is used. To define another viewstore location, use the following setting: ------- @@ -195,7 +195,7 @@ cleartool: Error: A registry entry already exists for "johndoe-mymachine-maven-m ** ClearCase Type By default, the ClearCase SCM provider uses commands appropriate for the full ClearCase version. If you are using ClearCase LT or - ClearCase UCM instead, you must specify this fact in the clearcase-settings.xml file. + ClearCase UCM instead, you must specify this fact in the <<<clearcase-settings.xml>>> file. ------- <clearcase-settings> @@ -204,7 +204,7 @@ cleartool: Error: A registry entry already exists for "johndoe-mymachine-maven-m ------- As ClearCase LT uses a predefined and unchangeable folder as the viewstore directory, you should also specify the viewstore - root location in the clearcase-settings.xml file: + root location in the <<<clearcase-settings.xml>>> file: ------- <clearcase-settings> http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/cvs.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/cvs.apt b/src/site/apt/cvs.apt index 7084663..faebc5e 100644 --- a/src/site/apt/cvs.apt +++ b/src/site/apt/cvs.apt @@ -30,9 +30,9 @@ SCM Implementation: CVS * General Info - Link : {{https://www.cvshome.org/}} + Link: {{https://www.cvshome.org/}} - License : GPL + License: GPL * SCM Url @@ -47,17 +47,17 @@ scm:cvs<delimiter><method>[<delimiter>username_password_servername_port]<delimit The following methods are supported: - * ext, connecting to a server using an external rsh program + * <<<ext>>>, connecting to a server using an external rsh program - * local, connecting to the local file system + * <<<local>>>, connecting to the local file system - * lserver, connecting to a local server + * <<<lserver>>>, connecting to a local server - * pserver, connecting to a password-authenticating server + * <<<pserver>>>, connecting to a password-authenticating server - * sspi, secure authentication (less supported by clients and servers, may require using native implementation, for more details see "How to choose the CVS provider implementation") + * <<<sspi>>>, secure authentication (less supported by clients and servers, may require using native implementation, for more details see "How to choose the CVS provider implementation") - * sserver, SSL connection method for CVS (only if cvs_native is used i.e. using -Dmaven.scm.provider.cvs.implementation=cvs_native with Maven) + * <<<sserver>>>, SSL connection method for CVS (only if cvs_native is used i.e. using -Dmaven.scm.provider.cvs.implementation=cvs_native with Maven) [] @@ -89,7 +89,7 @@ scm:cvs:sspi:cvs.apache.org:2222:/cvs/root:module By default, the pure java CVS provider is used (which may not support SSPI protocol), so you don't need a cvs client installed on your machine. In some case, you can want to use the installed CVS client (for example, CVSNT). To do it, you can change the implementation to use by settings the - 'maven.scm.provider.cvs.implementation' system property: + '<<<maven.scm.provider.cvs.implementation>>>' system property: ------- -Dmaven.scm.provider.cvs.implementation=cvs_native @@ -97,7 +97,7 @@ scm:cvs:sspi:cvs.apache.org:2222:/cvs/root:module * Provider Configuration - The provider configuration is defined in ${user.home}/.scm/cvs-settings.xml + The provider configuration is defined in <<<${user.home}/.scm/cvs-settings.xml>>> ** Compression level @@ -109,7 +109,7 @@ scm:cvs:sspi:cvs.apache.org:2222:/cvs/root:module </cvs-settings> ------- - If you don't want compression, you can define the system property 'maven.scm.cvs.use_compression'. + If you don't want compression, you can define the system property '<<<maven.scm.cvs.use_compression>>>'. ------- mvn -Dmaven.scm.cvs.use_compression=true scm:changelog @@ -117,7 +117,7 @@ mvn -Dmaven.scm.cvs.use_compression=true scm:changelog ** .cvsrc file - By default, maven-scm doesn't use .cvsrc file. If you want to use it, you should allow it inprovider configuration file. + By default, maven-scm doesn't use <<<.cvsrc>>> file. If you want to use it, you should allow it inprovider configuration file. ------- <cvs-settings> @@ -127,7 +127,7 @@ mvn -Dmaven.scm.cvs.use_compression=true scm:changelog ** Trace CVS commands - By default, maven-scm doesn't use '-t' global option of cvs command line to trace. If you want to use it, add the following lines in your provider configuration file : + By default, maven-scm doesn't use '<<<-t>>>' global option of cvs command line to trace. If you want to use it, add the following lines in your provider configuration file: ------- <cvs-settings> @@ -137,7 +137,7 @@ mvn -Dmaven.scm.cvs.use_compression=true scm:changelog ** Temporary CVS files - If you want to store CVS temporary files in a specific directory instead of default or value define in $TMPDIR, add the following lines in your provider configuration file : + If you want to store CVS temporary files in a specific directory instead of default or value define in <<<$TMPDIR>>>, add the following lines in your provider configuration file: ------- <cvs-settings> @@ -147,7 +147,7 @@ mvn -Dmaven.scm.cvs.use_compression=true scm:changelog ** Internal CVS variables - If you want to add some internal CVS variables to the cvs command line, , add the following lines in your provider configuration file : + If you want to add some internal CVS variables to the cvs command line, add the following lines in your provider configuration file: ------- <cvs-settings> http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/git.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/git.apt b/src/site/apt/git.apt index e969403..cf3577c 100644 --- a/src/site/apt/git.apt +++ b/src/site/apt/git.apt @@ -30,9 +30,9 @@ SCM Implementation: Git * General Info - Link : {{http://git-scm.com/}} + Link: {{http://git-scm.com/}} - License : GNU General Public License v2 + License: GNU General Public License v2 * SCM Url @@ -58,7 +58,7 @@ scm:git:file://localhost/path_to_repository * Different Fetch and Push URLs - In some cases a different URL has to be used for read and write operations. This can happen if e.g. fetch is performed via the http protocol, but writing to the repository is only possible via ssh. In this case both URLs may be written into the <developerConnection> tag. The fetch URL has to be prefixed with <<<[fetch=]>>> and the push URL with <<<[push=]>>> + In some cases a different URL has to be used for read and write operations. This can happen if e.g. fetch is performed via the http protocol, but writing to the repository is only possible via ssh. In this case both URLs may be written into the <developerConnection> tag. The fetch URL has to be prefixed with <<<[fetch=]>>> and the push URL with <<<[push=]>>> * Example: @@ -68,7 +68,7 @@ scm:git:file://localhost/path_to_repository * Working with branches - Since version 1.3, we assume that the name of the branch in the upstream repo is the same as the name of the current local branch. So whenever you invoke a maven-scm action which has to access the upstream repository, e.g. start a release, you should be on that very branch. + Since version 1.3, we assume that the name of the branch in the upstream repo is the same as the name of the current local branch. So whenever you invoke a maven-scm action which has to access the upstream repository, e.g. start a release, you should be on that very branch. In other words: If no branch is specified manually, every git-fetch, git-pull, git-push, etc will always work on the branch in the upstream repository which has the same branch name as your current local branch @@ -79,7 +79,7 @@ git push pushUrl currentBranch:currentBranch * Provider Configuration - The provider configuration is defined in ${user.home}/.scm/git-settings.xml. + The provider configuration is defined in <<<${user.home}/.scm/git-settings.xml>>>. ------- <git-settings> http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/jazz.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/jazz.apt b/src/site/apt/jazz.apt index 84c707d..d4e4995 100644 --- a/src/site/apt/jazz.apt +++ b/src/site/apt/jazz.apt @@ -2,29 +2,29 @@ SCM Implementation: Jazz ------ Chris Graham - -------------- + ------ 2012-03-19 - -------------- - - ~~ Licensed to the Apache Software Foundation (ASF) under one - ~~ or more contributor license agreements. See the NOTICE file - ~~ distributed with this work for additional information - ~~ regarding copyright ownership. The ASF licenses this file - ~~ to you under the Apache License, Version 2.0 (the - ~~ "License"); you may not use this file except in compliance - ~~ with the License. You may obtain a copy of the License at - ~~ - ~~ http://www.apache.org/licenses/LICENSE-2.0 - ~~ - ~~ Unless required by applicable law or agreed to in writing, - ~~ software distributed under the License is distributed on an - ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY - ~~ KIND, either express or implied. See the License for the - ~~ specific language governing permissions and limitations - ~~ under the License. - - ~~ NOTE: For help with the syntax of this file, see: - ~~ http://maven.apache.org/doxia/references/apt-format.html + ------ + +~~ Licensed to the Apache Software Foundation (ASF) under one +~~ or more contributor license agreements. See the NOTICE file +~~ distributed with this work for additional information +~~ regarding copyright ownership. The ASF licenses this file +~~ to you under the Apache License, Version 2.0 (the +~~ "License"); you may not use this file except in compliance +~~ with the License. You may obtain a copy of the License at +~~ +~~ http://www.apache.org/licenses/LICENSE-2.0 +~~ +~~ Unless required by applicable law or agreed to in writing, +~~ software distributed under the License is distributed on an +~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +~~ KIND, either express or implied. See the License for the +~~ specific language governing permissions and limitations +~~ under the License. + +~~ NOTE: For help with the syntax of this file, see: +~~ http://maven.apache.org/doxia/references/apt-format.html SCM Implementation: Jazz @@ -32,26 +32,26 @@ SCM Implementation: Jazz This SCM provider wrappers the underlying command line tool "scm" that is provided as part of Jazz SCM offering. As such, this provider is subject to the capabilities provided by the scm tool. - + The scm tool itself is documented at: - + *V2.0.0 {{http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.team.scm.doc/topics/r_scm_cli_scm.html}} - + *V3.0 {{http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0/topic/com.ibm.team.scm.doc/topics/r_scm_cli_scm.html}} - + * V3.0.1 {{http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.team.scm.doc/topics/r_scm_cli_scm.html}} [] - + Jazz is available from: - + Link: {{http://jazz.net/}} License: Free IBM Rational Team Concert is IBM commercial offering based upon the Jazz base platform. This provider may also be used with RTC. - + Link: {{http://www-01.ibm.com/software/rational/products/rtc/}} License: Commercial @@ -61,7 +61,7 @@ SCM Implementation: Jazz The Jazz SCM source control command line tools are installed in JazzInstallDir/scmtools/eclipse, which may not have been added to your default path. You must make sure that this path is available to maven when using this provider. - + Additionally, the user used to log onto the Jazz SCM server must be assigned a {{{http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.repository.web.admin.doc/topics/c_license_mgmt_over.html}Developer Client Access License}}. 10 developer licenses are available for free from {{http://jazz.net/}}. @@ -72,9 +72,9 @@ SCM Implementation: Jazz * <username;password> May be provided directly in the pom, or using the server_name:port to obtain the details from the user's settings.xml file. - + * http[s]://server_name:port/jazzPath Specify the jazz server and path to connect to. - + * <repositoryWorkspace> The name of the user's remote repository workspace used to checkin to, or load from. [] @@ -102,96 +102,96 @@ scm:jazz:https://server.name:9443/ccm:GPDBBuildWorkspace This provider only interacts with Jazz SCM, not all of the full capabilities of the full Jazz Server. This implementation is basically a wrapper for the Jazz SCM CLI tool, <<<scm>>>, and as such it is limited to the functionality provided by the underlying <<<scm>>> tool. - + There are many artifacts and concepts in Jazz SCM. Many of these artifacts and concepts are substantially different than how many other SCM providers work. - + We need some way to address these when we try to map the given maven-scm framework to Jazz SCM. Below is a list of these "artifacts / concepts" and roughly how they relate to the maven-scm framework. * Local Workspace - + * This corresponds to fileSet.getBasedir() and is the "baseDirectory" in which the SCM goals are performed against. * Url Path (ex: https://localhost) - + * This must be specified in the "SCM URL" of the pom.xml. - + * It's value will be stored in our implementation of the ScmProviderRepositoryWithHost.java. * Port (ex: 9443) - + * This must be specified in the "SCM URL" of the pom.xml. - + * It's value will be stored in our implementation of the ScmProviderRepositoryWithHost.java. * Jazz Path (ex: /jazz) - + * This must be specified in the "SCM URL" of the pom.xml. - + * It's value will be stored in our implementation of the ScmProviderRepositoryWithHost.java. * Repository Workspace - + * This must be specified in the "SCM URL" of the pom.xml. - + * It's value will be stored in our implementation of the ScmProviderRepositoryWithHost.java. * Username - + * This may be specified in the "SCM URL" of the pom.xml. - + * If not specified in the pom.xml, the username must be specified in a server entry of settings.xml. - + * It's value will be stored in our implementation of the ScmProviderRepositoryWithHost.java. * Password - + * This may be specified in the "SCM URL" of the pom.xml. - + * If not specified in the pom.xml, the username must be specified in a server entry of settings.xml. - + * It's value will be stored in our implementation of the ScmProviderRepositoryWithHost.java * Components - + * There is currently no concept of individual components in our implementation, or specifying them, they are implicitly obtained from the repository workspace. - + * Scm goals are currently assumed to be against all components in the repository workspace. * Baselines - + * Since we don't distinguish components, we do not use the concept of baselines. * Snapshots - + * We can use snapshots because we have a repository workspace defined in the SCM URL. - + * We assume that ScmVersion.getName() will correspond to a snapshot name. * Streams - + * We currently do not support the concept of streams in our provider. * Project Areas - + * We currently do not support the concept of project areas in our provider. * Team Areas - + * We currently do not support the concept of team areas in our provider. * Multiple Outgoing Change Sets - + * The SCM add operation performs a checkin, but it does not create a new change set. - + * The SCM checkin operation creates a new changeset, with the given comment and then checks the files in. - + * Delivering Change Sets - + * Changes are delivered/promoted as controlled by the <<<pushChanges>>> flag when we have a valid flow target. * Discarding Change Sets - + * We currently do not support the concept of discarding change sets in our provider. http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/local.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/local.apt b/src/site/apt/local.apt index 828cae1..b9dacac 100644 --- a/src/site/apt/local.apt +++ b/src/site/apt/local.apt @@ -30,9 +30,9 @@ SCM Implementation: File System * General Info - Link : - + Link: - - License : - + License: - * SCM Url http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/mercurial.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/mercurial.apt b/src/site/apt/mercurial.apt index 59da56a..ededb94 100644 --- a/src/site/apt/mercurial.apt +++ b/src/site/apt/mercurial.apt @@ -30,9 +30,9 @@ SCM Implementation: Mercurial * General Info - Link : {{http://www.selenic.com/mercurial/wiki/}} + Link: {{http://www.selenic.com/mercurial/wiki/}} - License : GNU General Public License + License: GNU General Public License "Mercurial: a fast, lightweight Source Control Management system designed for efficient handling of very large distributed projects." http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/perforce.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/perforce.apt b/src/site/apt/perforce.apt index b1f2e03..feb4add 100644 --- a/src/site/apt/perforce.apt +++ b/src/site/apt/perforce.apt @@ -30,9 +30,9 @@ SCM Implementation: Perforce * General Info - Link : {{http://www.perforce.com/}} + Link: {{http://www.perforce.com/}} - License : Commercial (It is licensed at no charge for use on open source projects.) + License: Commercial (It is licensed at no charge for use on open source projects.) * SCM Url http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/starteam.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/starteam.apt b/src/site/apt/starteam.apt index 2ede33d..28190d9 100644 --- a/src/site/apt/starteam.apt +++ b/src/site/apt/starteam.apt @@ -30,9 +30,9 @@ SCM Implementation: StarTeam * General Info - Link : {{http://www.borland.com/us/products/starteam/index.html}} + Link: {{http://www.borland.com/us/products/starteam/index.html}} - License : Commercial + License: Commercial * SCM Url http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/subversion.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/subversion.apt b/src/site/apt/subversion.apt index e7b6a7f..085259b 100644 --- a/src/site/apt/subversion.apt +++ b/src/site/apt/subversion.apt @@ -31,9 +31,9 @@ SCM Implementation: Subversion * General Info - Link : {{http://subversion.apache.org/}} + Link: {{http://subversion.apache.org/}} - License : Apache License, Version 2.0 + License: Apache License, Version 2.0 * SCM Url http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/synergy.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/synergy.apt b/src/site/apt/synergy.apt index 25f538d..7d1d330 100644 --- a/src/site/apt/synergy.apt +++ b/src/site/apt/synergy.apt @@ -30,9 +30,9 @@ SCM Implementation: CM/Synergy * General Info - Link : {{http://www.telelogic.com/Products/synergy/synergycm/index.cfm}} + Link: {{http://www.telelogic.com/Products/synergy/synergycm/index.cfm}} - License : Commercial + License: Commercial * SCM Url http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/tfs.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/tfs.apt b/src/site/apt/tfs.apt index c2fd3fc..6219317 100644 --- a/src/site/apt/tfs.apt +++ b/src/site/apt/tfs.apt @@ -1,7 +1,7 @@ ------ SCM Implementation: TFS - Team Foundation Server ------ -Mark Struberg + Mark Struberg ------ 2009-08-24 ------ @@ -30,9 +30,9 @@ SCM Implementation: TFS - Team Foundation Server * General Info - Link : {{http://www.microsoft.com/germany/visualstudio/products/team-system/}} + Link: {{http://www.microsoft.com/germany/visualstudio/products/team-system/}} - License : Commercial + License: Commercial * SCM Url http://git-wip-us.apache.org/repos/asf/maven-scm/blob/cb24f99e/src/site/apt/vss.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/vss.apt b/src/site/apt/vss.apt index bd36ac9..3e84c14 100644 --- a/src/site/apt/vss.apt +++ b/src/site/apt/vss.apt @@ -30,9 +30,9 @@ SCM Implementation: Visual Source Safe * General Info - Link : {{http://msdn.microsoft.com/ssafe/}} + Link: {{http://msdn.microsoft.com/ssafe/}} - License : Commercial + License: Commercial * SCM Url @@ -44,7 +44,7 @@ SCM Implementation: Visual Source Safe scm:vss|path_to_repository|/module_name ------- - The third variable is the path to the Visual Source Safe repository (where srcsafe.ini resides). + The third variable is the path to the Visual Source Safe repository (where <<<srcsafe.ini>>> resides). Note that a forward slash is necessary before the module name in the final variable. @@ -56,11 +56,11 @@ scm:vss|C:\Program Files\Microsoft Visual Studio\VSS|/SomeProject * Provider Configuration - The provider configuration is defined in ${user.home}/.scm/vss-settings.xml + The provider configuration is defined in <<<${user.home}/.scm/vss-settings.xml>>> ** VSS Installation directory - The provider needs to know the installation path of the ss.exe in order to fulfill VSS commands. The installation path can be set in two ways - either in the vss-settings.xml file: + The provider needs to know the installation path of the <<<ss.exe>>> in order to fulfill VSS commands. The installation path can be set in two ways - either in the <<<vss-settings.xml>>> file: ------- <vss-settings> @@ -76,4 +76,4 @@ scm:vss|C:\Program Files\Microsoft Visual Studio\VSS|/SomeProject mvn -DvssDirectory=ss_exe_directory scm:update ------- - In either case, ss_exe_directory should be set to the full path to the directory where ss.exe resides (e.g. C:\Program Files\Microsoft Visual Studio\VSS\bin). + In either case, <<<ss_exe_directory>>> should be set to the full path to the directory where <<<ss.exe>>> resides (e.g. <<<C:\Program Files\Microsoft Visual Studio\VSS\bin>>>).
