You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2017/03/10 07:43:44 UTC
svn commit: r1008063 - in /websites/staging/sling/trunk/content: ./
documentation/development/release-management.html
Author: buildbot
Date: Fri Mar 10 07:43:44 2017
New Revision: 1008063
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/development/release-management.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Mar 10 07:43:44 2017
@@ -1 +1 @@
-1786262
+1786294
Modified: websites/staging/sling/trunk/content/documentation/development/release-management.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/development/release-management.html (original)
+++ websites/staging/sling/trunk/content/documentation/development/release-management.html Fri Mar 10 07:43:44 2017
@@ -131,7 +131,7 @@ h2:hover > .headerlink, h3:hover > .head
<li><a href="#appendix-a-create-and-add-your-key-to-httpspeopleapacheorgkeysgroupslingasc">Appendix A: Create and Add your key to https://people.apache.org/keys/group/sling.asc</a></li>
<li><a href="#appendix-b-maven-and-scm-credentials">Appendix B: Maven and SCM credentials</a></li>
<li><a href="#appendix-c-deploy-bundles-on-the-sling-obr-obsolete">Appendix C: Deploy bundles on the Sling OBR (obsolete)</a></li>
-<li><a href="#appendix-d-deploy-maven-plugin-documentation">Appendix D: Deploy Maven plugin documentation</a></li>
+<li><a href="#appendix-d-deploy-maven-plugin-documentation-if-applicable">Appendix D: Deploy Maven plugin documentation (if applicable)</a></li>
</ul>
</div>
<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">¶</a></h2>
@@ -581,8 +581,9 @@ Then go to the CMS at <a href="https://c
update your checkout and then publish the site.</p>
</li>
</ol>
-<h2 id="appendix-d-deploy-maven-plugin-documentation">Appendix D: Deploy Maven plugin documentation<a class="headerlink" href="#appendix-d-deploy-maven-plugin-documentation" title="Permanent link">¶</a></h2>
-<p>For Maven plugins the Maven Site generated documentation with a list of supported goals and properties has to be published on the Slind website as well.</p>
+<h2 id="appendix-d-deploy-maven-plugin-documentation-if-applicable">Appendix D: Deploy Maven plugin documentation (if applicable)<a class="headerlink" href="#appendix-d-deploy-maven-plugin-documentation-if-applicable" title="Permanent link">¶</a></h2>
+<p>When releasing a Maven plugin, the Maven-generated documentation published under http://sling.apache.org/components/ needs
+to be updated.</p>
<p>This is currently supported for:</p>
<ul>
<li><code>maven-sling-plugin</code></li>
@@ -602,28 +603,28 @@ update your checkout and then publish th
</li>
<li>
-<p>Checkout the 'components' path of the Sling website</p>
+<p>Checkout the 'components' subtree of the Sling website</p>
<div class="codehilite"><pre>$ <span class="n">svn</span> <span class="n">checkout</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">infra</span><span class="o">/</span><span class="n">websites</span><span class="o">/</span><span class="n">production</span><span class="o">/</span><span class="n">sling</span><span class="o">/</span><span class="n">content</span><span class="o">/</span><span class="n">components</span>
</pre></div>
</li>
<li>
-<p>SVN-rename the generate documenation uploaded to <code><plugin-name>-archives/<plugin-name>-LATEST</code> to <code><plugin-name>-archives/<plugin-name>-<version></code></p>
+<p>svn move the <code><plugin-name></code> subfolder there under <plugin-name>-archives/<plugin-name>-<version>`, if not present yet</p>
</li>
<li>
-<p>SVN-remove the existing folder <code><plugin-name></code> and SVN-copy the folder <code><plugin-name>-archives/<plugin-name>-<version></code> to <code><plugin-name></code></p>
+<p>svn import the documentation generated by Maven site:site as `<plugin-name>' there.</p>
</li>
<li>
<p>Commit the changes.</p>
</li>
<li>
-<p>Check the documentation at <a href="http://sling.apache.org/components/">http://sling.apache.org/components/</a></p>
+<p>Check the results at <a href="http://sling.apache.org/components/">http://sling.apache.org/components/</a></p>
</li>
</ol>
-<p>For background information about this process see <a href="http://maven.apache.org/developers/website/deploy-component-reference-documentation.html">here</a>.</p>
+<p>For background information about this process see <a href="http://maven.apache.org/developers/website/deploy-component-reference-documentation.html">the Maven components reference documentation</a>.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1786262 by sseifert on Fri, 10 Mar 2017 00:16:33 +0000
+ Rev. 1786294 by bdelacretaz on Fri, 10 Mar 2017 07:43:25 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project