directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From elecha...@apache.org
Subject svn commit: r1757648 - /directory/site/trunk/content/apacheds/developer-guide.mdtext
Date Thu, 25 Aug 2016 10:05:13 GMT
Author: elecharny
Date: Thu Aug 25 10:05:13 2016
New Revision: 1757648

URL: http://svn.apache.org/viewvc?rev=1757648&view=rev
Log:
Added some missing information on teh ApacheDS dev guide

Modified:
    directory/site/trunk/content/apacheds/developer-guide.mdtext

Modified: directory/site/trunk/content/apacheds/developer-guide.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/developer-guide.mdtext?rev=1757648&r1=1757647&r2=1757648&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/developer-guide.mdtext (original)
+++ directory/site/trunk/content/apacheds/developer-guide.mdtext Thu Aug 25 10:05:13 2016
@@ -201,6 +201,11 @@ This deploys the release to a staging re
 
 ##### Build the Site
 
+We will now build the site. This will be done from the  <em>target/checkout</em>
directory :
+
+    :::text
+    $ cd target/checkout
+
 In order to generate the site, you have to comment some modules in the apacheds <em>pom.xml</em>
file :
 
     :::text
@@ -208,11 +213,13 @@ In order to generate the site, you have
     ...
     <!--module>installers-maven-plugin</module-->
     <!--module>installers</module-->
+    ...
+    <!--module>service</module-->
+
 
 Then you can start the maven command :
 
     :::text
-    $ cd target/checkout
     $ mvn site
 
 This creates the site and the Javadocs.
@@ -324,6 +331,12 @@ and copy the packages and signature to t
     $ cd target/checkout/target
     $ cp apacheds-parent-<version>-source-release.zip* ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22
 
+Last, not least, commit your changes
+
+    :::text
+    $ svn add ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22
+    $ svn ci ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22 -m "ApacheDS 2.0.M22 packages"
+
 ##### Test the new version
 
 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.
@@ -373,8 +386,6 @@ If the vote succeeds Apacheds project ca
 
 Go to [https://repository.apache.org/index.html#stagingRepositories](https://repository.apache.org/index.html#stagingRepositories)
and release the staging repository so all artifacts are published to Maven central.
 
-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>
-
 The sources, binaries and their signatures, have to be pushed in a place where they can be
downloaded by users. We use the [distribution](https://dist.apache.org/repos/dist/release/directory)
space for that purpose.
 
 Move the distribution packages (sources and binaries) to the dist SVN repository: https://dist.apache.org/repos/dist/release/directory/apacheds/dist/$(version)
@@ -449,9 +460,7 @@ You have to check in those directories :
     $ svn add <version>
     $ svn ci <version> -m "Injected <version> javadocs"
 
-Now, you have to update the staging site :
-
-    extpaths.txt
+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.
 
 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
 
@@ -467,9 +476,9 @@ Add the following line :
     apacheds/gen-docs/<version>
     ...
 
-then save and check in the file <em>.htaccess</em>
+then save and check in the file.
 
-We also have to update this file :
+We also have to update the <em>.htaccess</em> file :
 
     :::text
     $ cd ~/apacheds/staging/content/apacheds/gen-docs



Mime
View raw message