You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sl...@apache.org on 2026/08/19 16:21:09 UTC

(maven-wagon) 03/03: Replace the CVS examples with Git in the SCM wagon site

This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch wagon-3.x
in repository https://gitbox.apache.org/repos/asf/maven-wagon.git

commit 9dc97ef9a5fb90eeed766f671aea38469a745ef6
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Wed Aug 19 08:15:18 2026 +0200

    Replace the CVS examples with Git in the SCM wagon site
    
    maven-scm has had no CVS provider since 2.0.0-M1, so the CVS deployment
    example described a setup nobody can assemble. The section becomes the
    generic Git-server example; the gh-pages section stays as the GitHub
    variant that adds the branch configuration.
---
 wagon-providers/wagon-scm/src/site/markdown/index.md    |  7 +++----
 wagon-providers/wagon-scm/src/site/markdown/usage.md.vm | 12 ++++++------
 2 files changed, 9 insertions(+), 10 deletions(-)

diff --git a/wagon-providers/wagon-scm/src/site/markdown/index.md b/wagon-providers/wagon-scm/src/site/markdown/index.md
index affc927c..bad40199 100644
--- a/wagon-providers/wagon-scm/src/site/markdown/index.md
+++ b/wagon-providers/wagon-scm/src/site/markdown/index.md
@@ -28,16 +28,15 @@ under the License.
 
 This component is an implementation of Wagon provider for SCM (Source Control Management) systems, using [Maven SCM](/scm/).
 
-It enables Maven to use remote repositories stored in SCM systems (Subversion, CVS, ...) and to store Maven sites in SCMs.
+It enables Maven to use remote repositories stored in SCM systems (Subversion, Git, ...) and to store Maven sites in SCMs.
 
 # Features
 
-- Deploy files and directories to several SCM using Maven SCM (only tested with CVS and SVN)
-- Get files from several SCM using Maven SCM (only tested with CVS and SVN)
+- Deploy files and directories to several SCM using Maven SCM (only tested with Git and Subversion)
+- Get files from several SCM using Maven SCM (only tested with Git and Subversion)
 # Known issues
 
 - If the file is changed by the SCM, the checksum calculation may not work
     - SVN: when a file has properties `svn:eol-style` or `svn:keywords` set
-    - CVS: when keywords are expanded
 # See [maven-scm-publish-plugin](/plugins/maven-scm-publish-plugin/) to publish your site to SCM.
 
diff --git a/wagon-providers/wagon-scm/src/site/markdown/usage.md.vm b/wagon-providers/wagon-scm/src/site/markdown/usage.md.vm
index 71235252..5b149faf 100644
--- a/wagon-providers/wagon-scm/src/site/markdown/usage.md.vm
+++ b/wagon-providers/wagon-scm/src/site/markdown/usage.md.vm
@@ -80,10 +80,10 @@ Add the following extensions to your pom and use a wagon-scm url in the distribu
   </distributionManagement>
 ```
 
-Deploying your Maven site to CVS
+Deploying your Maven site to Git
 --------------------------------
 
-Same as before, but changing svnexe to cvsexe and using a CVS svn url.
+Same as before, but changing svnexe to gitexe and using a Git url.
 
 ```
   <build>
@@ -100,15 +100,15 @@ Same as before, but changing svnexe to cvsexe and using a CVS svn url.
       </extension>
       <extension>
         <groupId>org.apache.maven.scm</groupId>
-        <artifactId>maven-scm-provider-cvsexe</artifactId>
+        <artifactId>maven-scm-provider-gitexe</artifactId>
         <version>${mavenScmVersion}</version>
       </extension>
     </extensions>
   </build>
   <distributionManagement>
     <site>
-      <id>my.cvs.server</id>
-      <url>scm:cvs:ext:username@cvs.apache.org:/cvs/root:module</url>
+      <id>my.git.server</id>
+      <url>scm:git:ssh://git@git.example.org/myuser/myproject.git</url>
     </site>
   </distributionManagement>
 ```
@@ -116,7 +116,7 @@ Same as before, but changing svnexe to cvsexe and using a CVS svn url.
 Deploying your Maven site to GitHub's gh-pages
 ----------------------------------------------
 
-Same as before, but changing svnexe to gitexe and using a Git svn url.
+Same as before, but changing svnexe to gitexe and using a Git url.
 
 ```
   <build>