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 2024/12/27 11:36:52 UTC
(maven-wagon) branch docs1 created (now 3ea08df9)
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch docs1
in repository https://gitbox.apache.org/repos/asf/maven-wagon.git
at 3ea08df9 Drop outdated info about site publishing
This branch includes the following new commits:
new 3ea08df9 Drop outdated info about site publishing
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(maven-wagon) 01/01: Drop outdated info about site publishing
Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch docs1
in repository https://gitbox.apache.org/repos/asf/maven-wagon.git
commit 3ea08df9c748051a059b5e2fde608086ba77b236
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Fri Dec 27 12:36:45 2024 +0100
Drop outdated info about site publishing
---
wagon-providers/wagon-scm/src/site/apt/index.apt | 9 ++++----
.../wagon-scm/src/site/apt/usage.apt.vm | 24 +++-------------------
2 files changed, 7 insertions(+), 26 deletions(-)
diff --git a/wagon-providers/wagon-scm/src/site/apt/index.apt b/wagon-providers/wagon-scm/src/site/apt/index.apt
index 28617b68..be0ad3ac 100644
--- a/wagon-providers/wagon-scm/src/site/apt/index.apt
+++ b/wagon-providers/wagon-scm/src/site/apt/index.apt
@@ -30,14 +30,14 @@ Maven Wagon SCM
This component is an implementation of Wagon provider for SCM (Source Control Management) systems,
using {{{/scm/}Maven SCM}}.
-
+
It enables Maven to use remote repositories stored in SCM systems (Subversion, CVS, ...)
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)
@@ -49,6 +49,5 @@ Known issues
* CVS: when keywords are expanded
- * Generated site may have inconsistent newlines (see {{{https://issues.apache.org/jira/browse/MSITE-121}MSITE-121}}),
- preventing SCM check-in: <<prefer {{{/plugins/maven-scm-publish-plugin/}maven-scm-publish-plugin}} to
- publish your site to SCM>>
+
+See {{{/plugins/maven-scm-publish-plugin/}maven-scm-publish-plugin}} to publish your site to SCM.
diff --git a/wagon-providers/wagon-scm/src/site/apt/usage.apt.vm b/wagon-providers/wagon-scm/src/site/apt/usage.apt.vm
index 32a269d8..de5adf52 100644
--- a/wagon-providers/wagon-scm/src/site/apt/usage.apt.vm
+++ b/wagon-providers/wagon-scm/src/site/apt/usage.apt.vm
@@ -39,7 +39,7 @@ Maven Wagon SCM Usage
[]
and use URLs in the {{{/scm/scm-url-format.html}SCM format}}.
-
+
For non-subversion SCM, you can include the elements <<<scmVersionType>>> and <<<scmVersion>>> in your <<<settings.xml>>> file to
specify a branch or tag to use. The value of <<<scmVersionType>>> must be one of <<<branch>>> or <<<tag>>>.
There is no default value for <<<scmVersionType>>> so you <MUST> specify it with <<<scmVersion>>> in order
@@ -50,9 +50,6 @@ Deploying your Maven site to SCM
There are some <<shortcomings>> to simply using Wagon SCM provider with site plugin:
- * generated site may have inconsistent newlines (see {{{https://issues.apache.org/jira/browse/MSITE-121}MSITE-121}}),
- preventing SCM check-in,
-
* deploying site to SCM will require obsolete pages deletion, which is not done,
* site plugin way make one commit per file.
@@ -62,10 +59,8 @@ Deploying your Maven site to SCM
<<Prefer {{{http://maven.apache.org/plugins/maven-scm-publish-plugin/}maven-scm-publish-plugin}} to
publish your site to SCM>>
- <<Note for Maven 3 users:>> The site plugin behaves differently, require these
- be added as dependencies instead of extensions. See
- {{{/plugins/maven-site-plugin/examples/adding-deploy-protocol.html}
- Adding a Protocol to Deploy the Site}}.
+ The site plugin behaves differently, require these be added as dependencies instead of extensions. See
+ {{{/plugins/maven-site-plugin/examples/adding-deploy-protocol.html} Adding a Protocol to Deploy the Site}}.
* Deploying your Maven site to Subversion
@@ -205,16 +200,3 @@ Deploying your Maven site to SCM
</configuration>
</server>
------
-
-
-Using a SCM-based remote repository in Maven 2
-
-
-* Using a Subversion-based remote repository in Maven 2
-
- Not tested yet
-
-
-* Using a CVS-based remote repository in Maven 2
-
- Not tested yet