maven-scm-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From car...@apache.org
Subject svn commit: r1058449 - in /maven/scm/trunk: maven-scm-providers/maven-scm-provider-perforce/src/site/apt/index.apt src/site/apt/perforce.apt
Date Thu, 13 Jan 2011 08:03:28 GMT
Author: carlos
Date: Thu Jan 13 08:03:27 2011
New Revision: 1058449

URL: http://svn.apache.org/viewvc?rev=1058449&view=rev
Log:
Fix typos

Modified:
    maven/scm/trunk/maven-scm-providers/maven-scm-provider-perforce/src/site/apt/index.apt
    maven/scm/trunk/src/site/apt/perforce.apt

Modified: maven/scm/trunk/maven-scm-providers/maven-scm-provider-perforce/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-provider-perforce/src/site/apt/index.apt?rev=1058449&r1=1058448&r2=1058449&view=diff
==============================================================================
--- maven/scm/trunk/maven-scm-providers/maven-scm-provider-perforce/src/site/apt/index.apt
(original)
+++ maven/scm/trunk/maven-scm-providers/maven-scm-provider-perforce/src/site/apt/index.apt
Thu Jan 13 08:03:27 2011
@@ -28,7 +28,7 @@ Details
 
  The provider uses a few system properties to control how it operates.
 
- * <<<maven.scm.perforce.clientspec.name>>> - Allows you to override the
default name created by the provider.  By default the provider creates a clientspec with the
name "<username>-<hostname>-MavenSCM-<localpath>" to ensure uniqueness and
tracability.  If you want to use a pre-existing clientspec or conform to a corporate naming
standard, you can just pass the name here and the provider will use it instead.  This property
is most useful for scenarios where you want the clientspec to be retained, as with Continuum.
+ * <<<maven.scm.perforce.clientspec.name>>> - Allows you to override the
default name created by the provider.  By default the provider creates a clientspec with the
name "<username>-<hostname>-MavenSCM-<localpath>" to ensure uniqueness and
traceability.  If you want to use a pre-existing clientspec or conform to a corporate naming
standard, you can just pass the name here and the provider will use it instead.  This property
is most useful for scenarios where you want the clientspec to be retained, as with Continuum.
 
  * <<<maven.scm.persistcheckout>>> - Controls whether the Perforce provider
will delete
  the clientspec once the operation is done.  In the case where we just want to check out
a source tree to a temporary directory (like with the release plugin), we want this to be
false since there is no reason to keep the clientspec around.  On the other hand, when used
with Continuum, you want to remember the checkout so that repeated syncs take a minimum of
time.  The default is false.

Modified: maven/scm/trunk/src/site/apt/perforce.apt
URL: http://svn.apache.org/viewvc/maven/scm/trunk/src/site/apt/perforce.apt?rev=1058449&r1=1058448&r2=1058449&view=diff
==============================================================================
--- maven/scm/trunk/src/site/apt/perforce.apt (original)
+++ maven/scm/trunk/src/site/apt/perforce.apt Thu Jan 13 08:03:27 2011
@@ -51,7 +51,8 @@ scm:perforce://depot/modules/myproject
 -------
 
 * Associating Jobs with checkin changelist
-    Many Perforce installation have a 'require job' rule/trigger turned on.
+
+    Many Perforce installations have a 'require job' rule/trigger turned on.
     To allow checkin when such a rule is defined, the system property maven.scm.jobs
     can be set to specify a job that will be associated with the changelist on checkin.
     Handling of multiple jobs is currently not implemented.



Mime
View raw message