Author: hboutemy
Date: Wed Aug 19 22:57:29 2015
New Revision: 1696687
URL: http://svn.apache.org/r1696687
Log:
added a link to MPOM-80
Modified:
maven/site/trunk/content/apt/developers/website/deploy-component-reference-documentation.apt
Modified:
maven/site/trunk/content/apt/developers/website/deploy-component-reference-documentation.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/content/apt/developers/website/deploy-component-reference-documentation.apt?rev=1696687&r1=1696686&r2=1696687&view=diff
==============================================================================
---
maven/site/trunk/content/apt/developers/website/deploy-component-reference-documentation.apt
(original)
+++
maven/site/trunk/content/apt/developers/website/deploy-component-reference-documentation.apt
Wed Aug 19 22:57:29 2015
@@ -30,7 +30,7 @@
Introduction
This document gives step-by-step instructions for deploying
- Maven components reference documentation inside the Maven
{{{http://maven.apache.org}http://maven.apache.org}} website.
+ Maven components reference documentation inside the Maven
{{{http://maven.apache.org/}http://maven.apache.org/}} website.
See {{{./index.html}Maven website introduction}} for instructions on the
whole website publication (main site content + components).
@@ -50,11 +50,11 @@ How components reference documentation p
* Staging component reference documentation
- Reference documentation of a component is staged in
<<<http://maven.apache.org/xxx-archives/yyy-LATEST>>>, where <<<yyy>>> is the
+ Reference documentation of a component is staged in
<<<http://maven.apache.org/xxx-archives/yyy-LATEST/>>>, where <<<yyy>>> is the
component name and <<<xxx>>> can be:
* the component type, like <<<shared>>>, <<<plugins>>>, <<<skins>>>, ... (see
- {{/shared-archives/}}, {{/plugins-archives/}}, {{/skins-archives/}})
+ {{/shared-archives/}}, {{/plugins-archives/}}, {{/plugin-tools-archives/}},
{{/pom-archives/}}, {{/scm-archives/}}, {{/skins-archives/}},
{{/surefire-archives/}}, ...)
* the component name for standalone components, like <<<archetype>>>,
<<<plugin-tools>>>, <<<surefire>>>, <<<wagon>>>, ...
(see {{/archetype-archives/}}, {{/plugin-tools-archives/}},
{{/surefire-archives/}}, {{/wagon-archives/}})
@@ -95,7 +95,7 @@ mvn scm-publish:publish-scm
<<Notice>>: content is in fact published to {{/components/}} directory,
and rewrite rules in <<<.htaccess>>> detect files not found in main site to
try
- {{/components/}} content instead.
+ {{/components/}} content instead (see
{{{https://issues.apache.org/jira/browse/MPOM-80}MPOM-80}}.
* Publishing versioned component reference documentation
@@ -156,4 +156,4 @@ svnmucc -m "Publish yyy $version documen
<<Notice>>: if you forget about updating the index page, dist-tool has a
{{{https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-check-index-page.html}report
run daily}}
- that will gently send a failure notification on [email protected].
+ that will gently send a failure notification on [email protected].
\ No newline at end of file