svn commit: r995878 - in /websites/staging/directory/trunk/content: ./ apacheds/developer-guide.html

[bu...@apache.org]

Author: buildbot
Date: Thu Aug 25 10:05:20 2016
New Revision: 995878

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/developer-guide.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Aug 25 10:05:20 2016
@@ -1 +1 @@
-1755121
+1757648

Modified: websites/staging/directory/trunk/content/apacheds/developer-guide.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/developer-guide.html (original)
+++ websites/staging/directory/trunk/content/apacheds/developer-guide.html Thu Aug 25 10:05:20 2016
@@ -318,17 +318,23 @@ $ mvn release:prepare
 
 <p>This deploys the release to a staging repository. Go to <a href="https://repository.apache.org/index.html#stagingRepositories">Staging Repositories</a> and close the staging repository.</p>
 <h5 id="build-the-site">Build the Site<a class="headerlink" href="#build-the-site" title="Permanent link">&para;</a></h5>
+<p>We will now build the site. This will be done from the  <em>target/checkout</em> directory :</p>
+<div class="codehilite"><pre>$ cd target/checkout
+</pre></div>
+
+
 <p>In order to generate the site, you have to comment some modules in the apacheds <em>pom.xml</em> file :</p>
 <div class="codehilite"><pre>&lt;!--module&gt;all&lt;/module--&gt;
 ...
 &lt;!--module&gt;installers-maven-plugin&lt;/module--&gt;
 &lt;!--module&gt;installers&lt;/module--&gt;
+...
+&lt;!--module&gt;service&lt;/module--&gt;
 </pre></div>
 
 
 <p>Then you can start the maven command :</p>
-<div class="codehilite"><pre>$ cd target/checkout
-$ mvn site
+<div class="codehilite"><pre>$ mvn site
 </pre></div>
 
 
@@ -436,6 +442,12 @@ $ cp apacheds-parent-&lt;version&gt;-sou
 </pre></div>
 
 
+<p>Last, not least, commit your changes</p>
+<div class="codehilite"><pre>$ svn add ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22
+$ svn ci ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22 -m &quot;ApacheDS 2.0.M22 packages&quot;
+</pre></div>
+
+
 <h5 id="test-the-new-version">Test the new version<a class="headerlink" href="#test-the-new-version" title="Permanent link">&para;</a></h5>
 <p>The best way to do that is to download the sources, extract them, build the server and the installers, and check if the installers are correctly working. Then check that the server is correctly running.</p>
 <h5 id="create-the-installers">Create the installers<a class="headerlink" href="#create-the-installers" title="Permanent link">&para;</a></h5>
@@ -473,7 +485,6 @@ $ cp apacheds-&lt;version&gt;* ~/apached
 <h5 id="release">Release<a class="headerlink" href="#release" title="Permanent link">&para;</a></h5>
 <p>If the vote succeeds Apacheds project can be released.</p>
 <p>Go to <a href="https://repository.apache.org/index.html#stagingRepositories">https://repository.apache.org/index.html#stagingRepositories</a> and release the staging repository so all artifacts are published to Maven central.</p>
-<p>Move the distribution packages (sources and binaries) to the dist SVN repository: <em>https://dist.apache.org/repos/dist/release/directory/apacheds/dist/$(version)</em></p>
 <p>The sources, binaries and their signatures, have to be pushed in a place where they can be downloaded by users. We use the <a href="https://dist.apache.org/repos/dist/release/directory">distribution</a> space for that purpose.</p>
 <p>Move the distribution packages (sources and binaries) to the dist SVN repository: https://dist.apache.org/repos/dist/release/directory/apacheds/dist/$(version)</p>
 <p>If you haven't checked out this space, do it now :</p>
@@ -543,11 +554,7 @@ $ svn ci &lt;version&gt; -m &quot;Inject
 </pre></div>
 
 
-<p>Now, you have to update the staging site :</p>
-<div class="codehilite"><pre><span class="n">extpaths</span><span class="p">.</span><span class="n">txt</span>
-</pre></div>
-
-
+<p>Now, you have to update the staging site, but first, do a <em>svn up</em>. the  you have to update the <em>extpaths.txt</em> file.</p>
 <p>This file list the file on the production site that will not be overriden by the publication of the staging site. It has to be updated</p>
 <div class="codehilite"><pre>$ cd ~/apacheds/staging/content/
 $ vi extpaths.txt
@@ -562,8 +569,8 @@ apacheds/gen-docs/&lt;version&gt;
 </pre></div>
 
 
-<p>then save and check in the file <em>.htaccess</em></p>
-<p>We also have to update this file :</p>
+<p>then save and check in the file.</p>
+<p>We also have to update the <em>.htaccess</em> file :</p>
 <div class="codehilite"><pre>$ cd ~/apacheds/staging/content/apacheds/gen-docs
 $ vi .htaccess
 </pre></div>