svn commit: r1022419 - in /websites/staging/directory/trunk/content: ./ api/coding-standards.html api/developer-guide.html

[bu...@apache.org]

Author: buildbot
Date: Mon Dec 18 21:15:08 2017
New Revision: 1022419

Log:
Staging update by buildbot for directory

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

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 18 21:15:08 2017
@@ -1 +1 @@
-1818625
+1818626

Modified: websites/staging/directory/trunk/content/api/coding-standards.html
==============================================================================
--- websites/staging/directory/trunk/content/api/coding-standards.html (original)
+++ websites/staging/directory/trunk/content/api/coding-standards.html Mon Dec 18 21:15:08 2017
@@ -168,7 +168,7 @@ h2:hover > .headerlink, h3:hover > .head
 <p>Welcome to you fellow developer.  You've maybe been elected committer on the project, or want to contribute some code / patch? This is great news! However, in order to be able to share your 'vision' with your code, some rules must be followed.</p>
 <p>Hey, remember that those rules are not the best nor the worst, they are pretty much what they are for historical reasons, or for technical reasons, however, please, accept them as they are, and avoid religious war (please, oh please, no mail to say "WTF ? You are using spaces instead of tab ??? How stupid is this rule etc etc.) Rules are <em><em>alway</em>s</em> stupid, but smart people follow them ;)</p>
 <p><strong>eclipse IDE</strong></p>
-<p>Eclipse users can import those two files to enfore the code formating : <a href="http://svn.apache.org/repos/asf/directory/project/trunk/resources/formatting.xml">formatting.xml</a> and <a href="http://svn.apache.org/repos/asf/directory/project/trunk/resources/codetemplates.xml">codetemplates.xml</a></p>
+<p>Eclipse users can import those two files to enfore the code formating : <a href="https://github.com/apache/directory-project/blob/master/resources/formatting.xml">formatting.xml</a> and <a href="https://github.com/apache/directory-project/blob/master/resources/codetemplates.xml">codetemplates.xml</a></p>
 <p><strong>IDEA IDE</strong></p>
 <p>IDEA users can import <a href="settings.jar">this file</a> to enfore the code formating.</p>
 <h2 id="headers">Headers<a class="headerlink" href="#headers" title="Permanent link">&para;</a></h2>

Modified: websites/staging/directory/trunk/content/api/developer-guide.html
==============================================================================
--- websites/staging/directory/trunk/content/api/developer-guide.html (original)
+++ websites/staging/directory/trunk/content/api/developer-guide.html Mon Dec 18 21:15:08 2017
@@ -202,6 +202,7 @@ h2:hover > .headerlink, h3:hover > .head
 <li>Use the new <em>Enum</em> type !</li>
 </ul>
 <h2 id="releasing-the-ldap-api">Releasing the LDAP API<a class="headerlink" href="#releasing-the-ldap-api" title="Permanent link">&para;</a></h2>
+<p><strong>Note: The release guide needs to be updated after git migration!</strong></p>
 <p>Here is a guide on how to cut a new release. This is a long process, expect it to last a couple of hours !</p>
 <p>First, you need to have a recent version of Maven (we are using 3.0.4) and a recent version of the JDK (1.7 is ok, it should also build with 1.6).</p>
 <h3 id="maven-settings">Maven Settings<a class="headerlink" href="#maven-settings" title="Permanent link">&para;</a></h3>