misc enhancements
git-svn-id: https://svn.apache.org/repos/asf/maven/plugins/trunk@1595674 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/src/site/apt/examples/importing-maven-site.apt b/src/site/apt/examples/importing-maven-site.apt
index 8acd3fa..3d44d9b 100644
--- a/src/site/apt/examples/importing-maven-site.apt
+++ b/src/site/apt/examples/importing-maven-site.apt
@@ -39,7 +39,7 @@
+--------
# configuration
ORIG_PATH=/www/maven.apache.org
-DEST_SVN_BASE=https://svn.apache.org/repos/infra/websites/production/maventest/content
+DEST_SVN_BASE=https://svn.apache.org/repos/infra/websites/production/maven/content
ARTIFACT=maven-clean-plugin
DIR=plugins/${ARTIFACT}
diff --git a/src/site/apt/index.apt.vm b/src/site/apt/index.apt.vm
index af6c851..bab8b58 100644
--- a/src/site/apt/index.apt.vm
+++ b/src/site/apt/index.apt.vm
@@ -31,13 +31,13 @@
The maven-scm-publish-plugin is a utility plugin to allow publishing Maven
website to any supported SCM.
The primary goal was to have an utility plugin to allow Apache projects
- to publish Maven websites via the ASF svnpubsub system
+ to publish Maven websites via the ASF svnpubsub system.
In addition to SCM operations, it takes care to fix newline inconsistencies
generated by <<<maven-site-plugin>>> (see {{{https://jira.codehaus.org/browse/MSITE-121}MSITE-121}}),
which prevents simple content import to SCM.
- The plugin has been tested with git scm too and by example can push content for github pages too.
+ The plugin has been tested with git scm too and by example can push content for github pages.
* Implementation
@@ -50,7 +50,7 @@
Then locally staged content is applied to the check-out, issuing
appropriate SCM commands to add and delete entries, followed by a
- checkin.
+ check-in.
The <<scmpublish.dryRun>> parameter to the plugin avoids all
SCM operations, and simply logs out the added, deleted,
@@ -62,11 +62,11 @@
* Publishing any content to SCM
- Even without any pom.xml/Maven project, you can update SCM content with
+ Even without any <<<pom.xml>>>/Maven project, you can update SCM content with
a local content:
+-------+
-mvn scm-publish:publish-scm -Dscmpublish.pubScmUrl=scm:... -Dscmpublish.content=...path-to-content...
+mvn scm-publish:publish-scm -Dscmpublish.pubScmUrl=scm:<scm-provider>... -Dscmpublish.content=...path-to-content...
+-------+
SCM content will be checked-out to a temporary directory, then local content will
@@ -81,8 +81,8 @@
There are 2 known limitations:
- * For svn the plugin can create the initial SCM directory if it does not exist. But for git by example if you use a branch,
- the branch won't be created, you have to create it manually.
+ * for svn, the plugin can create the initial SCM directory if it does not exist. But for git by example, if you use a branch,
+ the branch won't be created: you have to create it manually,
* the plugin works well for multi-module websites publishing to a complete directory:
you just need to publish <<<mvn site:stage>>> content. But if one module does not publish
@@ -99,7 +99,7 @@
To reach such a dream, there are some steps:
- * fix inconsistent newlines generated by <<<maven-site-plugin>>> (caused by site.vm template and
+ * fix inconsistent newlines generated by <<<maven-site-plugin>>> (caused by <<<site.vm>>> template and
resources taken from skin jar without fixing newlines): {{{https://jira.codehaus.org/browse/MSITE-121}MSITE-121}}
is fixed in (future) maven-site-plugin 3.4,
@@ -108,4 +108,4 @@
[]
- Then this plugin will be outdated, replaced by natural <<<maven-site-plugin:deploy>>> goal.
+ Then this plugin would be outdated, replaced by natural <<<maven-site-plugin:deploy>>> goal.
diff --git a/src/site/apt/various-tips.apt.vm b/src/site/apt/various-tips.apt.vm
index 688c5de..bac3f7b 100644
--- a/src/site/apt/various-tips.apt.vm
+++ b/src/site/apt/various-tips.apt.vm
@@ -36,7 +36,7 @@
scm:<scm_provider><delimiter><provider_specific_part>
+----------------
- Example for svn: <<<scm:svn:https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins/maven-scm-publish-plugin/>>>
+ Example for svn: <<<scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/content/plugins/maven-scm-publish-plugin/>>>
And configure is as it:
@@ -44,7 +44,7 @@
<distributionManagement>
<site>
<id>site_id</id>
- <url>scm:svn:https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins/maven-scm-publish-plugin/</url>
+ <url>scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/content/plugins/maven-scm-publish-plugin/</url>
</site>
</distributionManagement>
+----------------
