directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r957126 [17/18] - in /websites/staging/directory/trunk/content: ./ apacheds/ apacheds/advanced-ug/ apacheds/basic-ug/ apacheds/configuration/ apacheds/kerberos-ug/ api/ api/download/ api/groovy-api/ api/user-guide/ escimo/ fortress/ fortres...
Date Sun, 05 Jul 2015 22:34:38 GMT
Modified: websites/staging/directory/trunk/content/original-project-proposal.html
==============================================================================
--- websites/staging/directory/trunk/content/original-project-proposal.html (original)
+++ websites/staging/directory/trunk/content/original-project-proposal.html Sun Jul  5 22:34:35 2015
@@ -101,7 +101,7 @@
     <ul>
         <li><a href="./apacheds/downloads.html">ApacheDS 2.0.0-M20</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./studio/downloads.html">Studio 2.0.0-M9</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
-        <li><a href="./api/downloads.html">LDAP API 1.0.0-M30</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
+        <li><a href="./api/downloads.html">LDAP API 1.0.0-M31</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./mavibot/downloads.html">Mavibot 1.0.0-M7</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./fortress/downloads.html">Fortress 1.0-RC40</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li-->
         <!-- <li><a href="./escimo/downloads.html">eSCIMo 1.0.0-M1</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li> -->
@@ -162,8 +162,19 @@
 
 
 
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <p>This is the original project proposal for the incubation of the Apache Directory Project sent to the Apache Incubator by Alex Karasulu.  Although old (September 2003), it is still worth reading as the original vision of the project.  It's a piece of history. </p>
-<h1 id="proposal-for-an-apache-directory-project">Proposal for an Apache Directory Project</h1>
+<h1 id="proposal-for-an-apache-directory-project">Proposal for an Apache Directory Project<a class="headerlink" href="#proposal-for-an-apache-directory-project" title="Permanent link">&para;</a></h1>
 <p>10 Sept 2003, Alex Karasulu (akarasulu@apache.org) LDAPd Group Founder</p>
 <ul>
 <li><a href="#section-0-rationale">Rationale</a></li>
@@ -174,7 +185,7 @@
 <li><a href="#section-5-apache-sponsoring-individuals">Apache Sponsoring Individuals</a></li>
 <li><a href="#section-6-incubation-exit-criteria">Incubation Exit Criteria</a></li>
 </ul>
-<h2 id="section-0-rationale">Section 0 : Rationale</h2>
+<h2 id="section-0-rationale">Section 0 : Rationale<a class="headerlink" href="#section-0-rationale" title="Permanent link">&para;</a></h2>
 <p>The geometric growth of networks, services, distributed systems, and their components has brought about a revival of interest in directories. Directories are no longer considered commodity products used to store a phone book or list of users. Directories and LDAP have grown into a critical technology that will inevitably become a cornerstone of distributed systems. Several software giants like BEA, SUN, and Microsoft have already demonstrated their belief in this outcome by heavily integrating their products with directories. Directory and naming systems are being used in everything from a simplified form for J2EE configuration to full-blown enterprise directories, within identity management systems and distributed computing platforms like JINI.</p>
 <p>The overhead of managing several copies of relatively static information across systems and enterprises is daunting and introduces the potential for data inconsistency. The frequently replicated user and group tables in almost every database driven application alone is a testament to this fact. When multiple systems have to inter operate, they must share access to common information, and directories are the best storage paradigm for rapidly accessing this type of data. Whether the information to be stored, is a component's configuration, a user's security profile, a business rule or a business process, directories are the place to store it for centralized management, and distribution across systems.</p>
 <p>To date, a fully compliant pure Java open source LDAPv3 server has not yet been written. This is partially due to the fact that a practical stateful protocol server in Java was virtually impossible until the introduction of the NIO packages in the 1.4 SDK. LDAP, as a stateful protocol, manages client state through a TCP socket connection. The socket connection persists through several client requests and server responses tying them together under a logical session or conversation. Before the introduction of non-blocking IO in the NIO packages of the 1.4 SDK, a thread had to be dedicated to each socket to detect IO. A stateful protocol server written completely in Java, would have needed as many active threads as the number of concurrent clients. Theoretically, scalability would have been very poor; the performance curve would be asymptotic, degrading rapidly with an increase in the number of concurrent connections. To scale pure Java statefull protocol server implementations had 
 to wait until the Merlin release of the JDK.</p>
@@ -222,7 +233,7 @@
 <li><a href="http://www.ietf.org/rfc/rfc3296.txt">RFC3296</a> Named Subordinate References in Lightweight Directory Access Protocol (LDAP) Directories</li>
 <li><a href="http://www.ietf.org/rfc/rfc3383.txt">RFC3383</a> Internet Assigned Numbers Authority (IANA) considerations for the Lightweight Directory Access Protocol (LDAP) </li>
 </ul>
-<h3 id="section-01-criteria">Section 0.1 : Criteria</h3>
+<h3 id="section-01-criteria">Section 0.1 : Criteria<a class="headerlink" href="#section-01-criteria" title="Permanent link">&para;</a></h3>
 <p>We feel that this project has a good chance for success as the following project aspects are carefully considered :</p>
 <p>Meritocracy: The project will be meritocratic - the usual Apache meritocracy rules would apply.</p>
 <p>Community: The user community for this project is potentially massive. The initial developer community for this project consists of developers from Apache and LDAPd projects. The aim is for this community to grow considerably once this project enters the incubator.</p>
@@ -235,14 +246,14 @@
 <li>Home for Apache Directory Servers</li>
 <li>May also become home to an ASN.1 Encoding/Decoding? Library </li>
 </ul>
-<h3 id="section-02-warning-signs">Section 0.2 : Warning Signs</h3>
+<h3 id="section-02-warning-signs">Section 0.2 : Warning Signs<a class="headerlink" href="#section-02-warning-signs" title="Permanent link">&para;</a></h3>
 <p>We feel this project has a good chance for success as the following warning signs do not apply to the project we are proposing:</p>
 <p>Orphaned products: This project is starting with an existing code base which using lots of the high quality open source code out there which is ASF/BSD licensed.</p>
 <p>Inexperience with open source: The initial community is made up of existing Apache and LDAPd Group committers exclusively so the open source experience is there to varying degrees.</p>
 <p>Reliance on salaried developers: None of the initial developers are currently paid to work on the Directory Project.</p>
 <p>No ties to other Apache products: The Apache Directory Project is complementary to existing technologies at Apache. LDAPd currently uses Avalon and will eventually be used by james. LDAPd will eventually integrate into Geronimo. The Apache Directory Project will integrate with, and possibly subsume, Jakarta Commons Naming.</p>
 <p>A fascination with the Apache brand: The committers are interested in developing a healthy open source community around ASF/BSD licensed directory servers and their clients along with other JNDI accessible name spaces. Is Apache the right place? We think it is. Several Apache folks have already shown interest in LDAPd, the seed code base to be used for this project. In fact the LDAPd Group was initially approached by Apache to submit an Incubator proposal. LDAPd Group members voted unanimously to donate the code to Apache in an effort to build the next flagship server at Apache and much more. </p>
-<h2 id="section-1-scope-of-the-project">Section 1 : Scope of the Project</h2>
+<h2 id="section-1-scope-of-the-project">Section 1 : Scope of the Project<a class="headerlink" href="#section-1-scope-of-the-project" title="Permanent link">&para;</a></h2>
 <p>There are multiple goals for this Apache project:</p>
 <ul>
 <li>Promote a healthy open source community!</li>
@@ -258,24 +269,24 @@
 <li>Provide servers in standalone configurations as UNIX daemons or NT Services.</li>
 <li>Provide support for Directory Server embedding or integration with existing Apache servers like httpd, Slide, Tomcat, James and Geronimo. </li>
 </ul>
-<h2 id="section-2-initial-source">Section 2 : Initial Source</h2>
+<h2 id="section-2-initial-source">Section 2 : Initial Source<a class="headerlink" href="#section-2-initial-source" title="Permanent link">&para;</a></h2>
 <p>The initial code base from which to create the Apache Directory repository is contained mostly at Sourceforge under the LDAPd project accessible <a href="#">here</a>. This code base must assign copyright to the Apache Software Foundation. The code base will need to be licensed under The Apache Software Foundation license. The license file in every subproject will be changed to the Apache license. The current license is already an Apache "style" license, so this change is basically a change to name The ASF as the owner.</p>
 <p>The proposed TLP (after incubation) would have an one or more directory servers with multiple datastore backends, a JNDI context for J2EE configuration, JNDI service provider(s) for LDAP and other transports, State and Object Factories suitable for use in the various Context/DirContext? implementations, etc.</p>
 <p>Beside source code the LDAPd Group must transfer its IANA assigned ASN.1 Object Identifier to Apache Software Foundation.</p>
-<h2 id="section-3-asf-resources-to-be-created">Section 3 : ASF Resources to be Created</h2>
-<h3 id="section-31-mailing-lists">Section 3.1 : Mailing Lists</h3>
+<h2 id="section-3-asf-resources-to-be-created">Section 3 : ASF Resources to be Created<a class="headerlink" href="#section-3-asf-resources-to-be-created" title="Permanent link">&para;</a></h2>
+<h3 id="section-31-mailing-lists">Section 3.1 : Mailing Lists<a class="headerlink" href="#section-31-mailing-lists" title="Permanent link">&para;</a></h3>
 <ul>
 <li>directory-dev@incubator.apache.org </li>
 </ul>
-<h3 id="section-32-cvs-repositories">Section 3.2 : CVS Repositories</h3>
+<h3 id="section-32-cvs-repositories">Section 3.2 : CVS Repositories<a class="headerlink" href="#section-32-cvs-repositories" title="Permanent link">&para;</a></h3>
 <ul>
 <li>incubator-directory </li>
 </ul>
-<h3 id="section-33-bugzilla-or-preferably-jira">Section 3.3 : Bugzilla or (preferably) Jira</h3>
+<h3 id="section-33-bugzilla-or-preferably-jira">Section 3.3 : Bugzilla or (preferably) Jira<a class="headerlink" href="#section-33-bugzilla-or-preferably-jira" title="Permanent link">&para;</a></h3>
 <ul>
 <li>directory </li>
 </ul>
-<h2 id="section-4-initial-set-of-committers">Section 4 : Initial Set of Committers</h2>
+<h2 id="section-4-initial-set-of-committers">Section 4 : Initial Set of Committers<a class="headerlink" href="#section-4-initial-set-of-committers" title="Permanent link">&para;</a></h2>
 <p>All contributors must sign and submit a Contributors License Agreement. The following individuals are the contributors, and have signed and sent the agreement at one time or another:</p>
 <ul>
 <li>Alex Karasulu</li>
@@ -286,7 +297,7 @@
 <li>Henri Yandell</li>
 <li>Wes McKean? </li>
 </ul>
-<h2 id="section-5-apache-sponsoring-individuals">Section 5 : Apache Sponsoring Individuals</h2>
+<h2 id="section-5-apache-sponsoring-individuals">Section 5 : Apache Sponsoring Individuals<a class="headerlink" href="#section-5-apache-sponsoring-individuals" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Nicola Ken Barozzi (Apache Incubator)</li>
 <li>Noel J. Bergman (Apache James)</li>
@@ -294,7 +305,7 @@
 <li>Stephen McConnell? (Apache Avalon)</li>
 <li>James Strachan (Apache Geronimo) </li>
 </ul>
-<h2 id="section-6-incubation-exit-criteria">Section 6 : Incubation Exit Criteria</h2>
+<h2 id="section-6-incubation-exit-criteria">Section 6 : Incubation Exit Criteria<a class="headerlink" href="#section-6-incubation-exit-criteria" title="Permanent link">&para;</a></h2>
 <p>We feel this project should exit the incubator to a TLP using the domain name directory.apache.org should the following goals be met:</p>
 <p>Technical Goals:</p>
 <ul>

Modified: websites/staging/directory/trunk/content/privacy-policy.html
==============================================================================
--- websites/staging/directory/trunk/content/privacy-policy.html (original)
+++ websites/staging/directory/trunk/content/privacy-policy.html Sun Jul  5 22:34:35 2015
@@ -101,7 +101,7 @@
     <ul>
         <li><a href="./apacheds/downloads.html">ApacheDS 2.0.0-M20</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./studio/downloads.html">Studio 2.0.0-M9</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
-        <li><a href="./api/downloads.html">LDAP API 1.0.0-M30</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
+        <li><a href="./api/downloads.html">LDAP API 1.0.0-M31</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./mavibot/downloads.html">Mavibot 1.0.0-M7</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./fortress/downloads.html">Fortress 1.0-RC40</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li-->
         <!-- <li><a href="./escimo/downloads.html">eSCIMo 1.0.0-M1</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li> -->
@@ -162,7 +162,18 @@
 
 
 
-<h1 id="privacy-policy">Privacy Policy</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="privacy-policy">Privacy Policy<a class="headerlink" href="#privacy-policy" title="Permanent link">&para;</a></h1>
 <p>Information about your use of this website is collected using server access logs and a tracking cookie. The collected information consists of the following:</p>
 <ul>
 <li>The IP address from which you access the website;</li>

Modified: websites/staging/directory/trunk/content/references.html
==============================================================================
--- websites/staging/directory/trunk/content/references.html (original)
+++ websites/staging/directory/trunk/content/references.html Sun Jul  5 22:34:35 2015
@@ -101,7 +101,7 @@
     <ul>
         <li><a href="./apacheds/downloads.html">ApacheDS 2.0.0-M20</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./studio/downloads.html">Studio 2.0.0-M9</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
-        <li><a href="./api/downloads.html">LDAP API 1.0.0-M30</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
+        <li><a href="./api/downloads.html">LDAP API 1.0.0-M31</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./mavibot/downloads.html">Mavibot 1.0.0-M7</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./fortress/downloads.html">Fortress 1.0-RC40</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li-->
         <!-- <li><a href="./escimo/downloads.html">eSCIMo 1.0.0-M1</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li> -->
@@ -162,22 +162,33 @@
 
 
 
-<h1 id="references">References</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="references">References<a class="headerlink" href="#references" title="Permanent link">&para;</a></h1>
 <p>This page gathers some of the pointers you can find on the net about <em>ApacheDS</em> and <em>LDAP</em> :</p>
-<h2 id="on-wikipedia">On wikipedia:</h2>
+<h2 id="on-wikipedia">On wikipedia:<a class="headerlink" href="#on-wikipedia" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Apache_Directory">Joint placeholder for project, the server, Studio and more</a></li>
 <li><a href="https://en.wikipedia.org/wiki/List_of_LDAP_software">Overview of know ldap tools and servers</a></li>
 <li><a href="https://en.wikipedia.org/wiki/Directory_service">Overview of directory servers</a></li>
 <li><a href="https://fr.wikipedia.org/wiki/Apache_Directory_Server">French placeholder</a></li>
 </ul>
-<h2 id="on-ohloh-openhub">On OHLOH (openhub)</h2>
+<h2 id="on-ohloh-openhub">On OHLOH (openhub)<a class="headerlink" href="#on-ohloh-openhub" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="https://www.openhub.net/p/apacheds">Apache Directory Server 1.5</a></li>
 <li><a href="https://www.openhub.net/p/4873">Apache Directory Server 1.0</a></li>
 <li><a href="https://www.openhub.net/p/elbe">Apache Directory Studio</a></li>
 </ul>
-<h2 id="on-twitter">On Twitter:</h2>
+<h2 id="on-twitter">On Twitter:<a class="headerlink" href="#on-twitter" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="https://twitter.com/apacheds">ApacheDS official twitter account</a></li>
 </ul>

Modified: websites/staging/directory/trunk/content/sources.html
==============================================================================
--- websites/staging/directory/trunk/content/sources.html (original)
+++ websites/staging/directory/trunk/content/sources.html Sun Jul  5 22:34:35 2015
@@ -101,7 +101,7 @@
     <ul>
         <li><a href="./apacheds/downloads.html">ApacheDS 2.0.0-M20</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./studio/downloads.html">Studio 2.0.0-M9</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
-        <li><a href="./api/downloads.html">LDAP API 1.0.0-M30</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
+        <li><a href="./api/downloads.html">LDAP API 1.0.0-M31</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./mavibot/downloads.html">Mavibot 1.0.0-M7</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./fortress/downloads.html">Fortress 1.0-RC40</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li-->
         <!-- <li><a href="./escimo/downloads.html">eSCIMo 1.0.0-M1</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li> -->
@@ -162,16 +162,27 @@
 
 
 
-<h1 id="sources">Sources</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="sources">Sources<a class="headerlink" href="#sources" title="Permanent link">&para;</a></h1>
 <p>Sources for the Apache Directory projects are currently managed through <a href="http://subversion.tigris.org|subversion.tigris.org">Subversion</a>, except for Fortress Core which is <a href="http://git-wip-us.apache.org/">git base</a>. For each project you can find a detailed description how to checkout and build the source on the project documentation. This page is just a short overview.</p>
 <p><img alt="Subversion" src="images/subversion_logo.png" /></p>
-<h2 id="web-access-to-subversion">Web Access to Subversion</h2>
+<h2 id="web-access-to-subversion">Web Access to Subversion<a class="headerlink" href="#web-access-to-subversion" title="Permanent link">&para;</a></h2>
 <p>If you just want to browse the source code, you can use the <a href="http://svn.apache.org/viewvc/directory">web interface to Subversion</a>. This is current at all times.</p>
-<h2 id="web-access-to-git">Web access to Git</h2>
+<h2 id="web-access-to-git">Web access to Git<a class="headerlink" href="#web-access-to-git" title="Permanent link">&para;</a></h2>
 <p>If you just want to browse the source code, you can use the <a href="http://git-wip-us.apache.org/repos/asf?p=directory-fortress-core.git">web interface to Git</a>. This is current at all times.</p>
-<h2 id="normal-subversiongit-access">Normal Subversion/Git Access</h2>
+<h2 id="normal-subversiongit-access">Normal Subversion/Git Access<a class="headerlink" href="#normal-subversiongit-access" title="Permanent link">&para;</a></h2>
 <p>Anyone can check code out of Subversion. You only need to specify a username and password in order to update the Subversion repository, and only Directory committers have the permissions to do that. We run Subversion and Git over standard HTTP/HTTPS, so hopefully you won't have problems with intervening firewalls.</p>
-<h3 id="check-out-from-subversion-or-git">Check out from Subversion or Git</h3>
+<h3 id="check-out-from-subversion-or-git">Check out from Subversion or Git<a class="headerlink" href="#check-out-from-subversion-or-git" title="Permanent link">&para;</a></h3>
 <p>Again, anyone can do this. Use a command like:</p>
 <div class="codehilite"><pre><span class="n">svn</span> <span class="n">checkout</span> <span class="n">http</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">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">/</span><span class="n">apacheds</span><span class="o">/</span><span class="n">trunk</span><span class="o">-</span><span class="n">with</span><span class="o">-</span><span class="n">dependencies</span>
 </pre></div>
@@ -238,7 +249,7 @@
 </tr>
 </tbody>
 </table>
-<h3 id="commit-changes-to-subversion">Commit Changes to Subversion</h3>
+<h3 id="commit-changes-to-subversion">Commit Changes to Subversion<a class="headerlink" href="#commit-changes-to-subversion" title="Permanent link">&para;</a></h3>
 <p>Any Directory committer should have a shell account on svn.apache.org. Before you can commit, you'll need to set a Subversion password for yourself. To do that, log in to svn.apache.org and run the command svnpasswd.</p>
 <p>Once your password is set, you can use a command like this to commit:</p>
 <div class="codehilite"><pre><span class="n">svn</span> <span class="n">commit</span>
@@ -255,7 +266,7 @@
 For committers to be able to commit modification, they should have had checked out the project files using **https** instead of **http**.
 </DIV>
 
-<h3 id="commit-changes-to-git">Commit changes to Git</h3>
+<h3 id="commit-changes-to-git">Commit changes to Git<a class="headerlink" href="#commit-changes-to-git" title="Permanent link">&para;</a></h3>
 <p>Any Directory committer should have a shell account on git-wip-us.apache.org.</p>
 <p>You can use a command like this to push your changes to the repository :</p>
 <div class="codehilite"><pre><span class="n">git</span> <span class="n">push</span>
@@ -266,7 +277,7 @@ For committers to be able to commit modi
 For committers to be able to commit modification, they should have had checked out the project files using **https** instead of **http**.
 </DIV>
 
-<h2 id="read-only-git-repositories">Read Only Git Repositories</h2>
+<h2 id="read-only-git-repositories">Read Only Git Repositories<a class="headerlink" href="#read-only-git-repositories" title="Permanent link">&para;</a></h2>
 <p>There are also read only git repositories, which are mirroring the subversion repositories.</p>
 <table>
 <thead>
@@ -329,7 +340,7 @@ For committers to be able to commit modi
 </tr>
 </tbody>
 </table>
-<h2 id="web-site">Web Site</h2>
+<h2 id="web-site">Web Site<a class="headerlink" href="#web-site" title="Permanent link">&para;</a></h2>
 <p>The Web site itself is stored in a repository and can be updated easily. Let's see how it works.</p>
 <p>What is important here is that the pages are written using Markdown. Once a page has been modified, it can be committed, which will generate the static pages on a staging web site. When everything is checked and sounds correct, the staging site can be published on the production site, which will be pushed to the mirrors every hour. Here is the process :</p>
 <ul>
@@ -338,9 +349,9 @@ For committers to be able to commit modi
 <li>Check on the staging site to see if it's correct (see <a href="http://directory.staging.apache.org/">http://directory.staging.apache.org/</a>)</li>
 <li>Publish the site using the <a href="http://www.apache.org/dev/cmsref.html">Apache CMS</a></li>
 </ul>
-<h3 id="repository">Repository</h3>
+<h3 id="repository">Repository<a class="headerlink" href="#repository" title="Permanent link">&para;</a></h3>
 <p>All the web site can be fetched at <a href="http://svn.apache.org/repos/asf/directory/site/trunk/">https://svn.apache.org/repos/asf/directory/site/trunk/</a>. Be sure to use <em>https</em> in order to be able to commit your changes...</p>
-<h3 id="structure">Structure</h3>
+<h3 id="structure">Structure<a class="headerlink" href="#structure" title="Permanent link">&para;</a></h3>
 <p>The following structure is used :</p>
 <div class="codehilite"><pre><span class="n">cgi</span><span class="o">-</span><span class="n">bin</span>
 
@@ -373,7 +384,7 @@ For committers to be able to commit modi
 
 
 <p>Usually, you won't have to change the templates and lib section (except when cutting a release). Most of ypur updates will impact the content/<project> pages.</p>
-<h3 id="publishing-the-web-site">Publishing the web site</h3>
+<h3 id="publishing-the-web-site">Publishing the web site<a class="headerlink" href="#publishing-the-web-site" title="Permanent link">&para;</a></h3>
 <p>You have to install the <a href="http://www.apache.org/dev/cms.html#usage">CMS bookmarklet</a> for that. Then simply open the directory web site and click on the bookmarklet, enter your apache credentials (you have to be a committer) and click on the 'Publish' button.</p>
 <p>The best way to undertand how to use the CMS system is to follow <a href="https://www.youtube.com/watch?v=xcDZN3Lu6HA">this video</a>.</p>
 

Modified: websites/staging/directory/trunk/content/special-thanks.html
==============================================================================
--- websites/staging/directory/trunk/content/special-thanks.html (original)
+++ websites/staging/directory/trunk/content/special-thanks.html Sun Jul  5 22:34:35 2015
@@ -101,7 +101,7 @@
     <ul>
         <li><a href="./apacheds/downloads.html">ApacheDS 2.0.0-M20</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./studio/downloads.html">Studio 2.0.0-M9</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
-        <li><a href="./api/downloads.html">LDAP API 1.0.0-M30</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
+        <li><a href="./api/downloads.html">LDAP API 1.0.0-M31</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./mavibot/downloads.html">Mavibot 1.0.0-M7</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./fortress/downloads.html">Fortress 1.0-RC40</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li-->
         <!-- <li><a href="./escimo/downloads.html">eSCIMo 1.0.0-M1</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li> -->
@@ -162,8 +162,19 @@
 
 
 
-<h1 id="special-thanks">Special Thanks</h1>
-<h2 id="general-apache-sponsors">General Apache sponsors</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="special-thanks">Special Thanks<a class="headerlink" href="#special-thanks" title="Permanent link">&para;</a></h1>
+<h2 id="general-apache-sponsors">General Apache sponsors<a class="headerlink" href="#general-apache-sponsors" title="Permanent link">&para;</a></h2>
 <p>Without those sponsors, the ASF would simply not exist or sustain its activities :</p>
 <ul>
 <li><a href="http://www.apache.org/foundation/thanks.html">http://www.apache.org/foundation/thanks.html</a></li>
@@ -173,7 +184,7 @@
 <li><a href="http://www.apache.org/foundation/sponsorship.html">http://www.apache.org/foundation/sponsorship.html</a></li>
 </ul>
 <p>Thanks !</p>
-<h2 id="organizations-who-helped-our-project">Organizations who helped our project ...</h2>
+<h2 id="organizations-who-helped-our-project">Organizations who helped our project ...<a class="headerlink" href="#organizations-who-helped-our-project" title="Permanent link">&para;</a></h2>
 <p>We would also like to thank the organizations who provided some tools and images for free :</p>
 <table>
 <thead>

Modified: websites/staging/directory/trunk/content/studio/changelog.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/changelog.html (original)
+++ websites/staging/directory/trunk/content/studio/changelog.html Sun Jul  5 22:34:35 2015
@@ -151,8 +151,19 @@
 
 
 
-<h1 id="changelog">ChangeLog</h1>
-<h2 id="apache-directory-studio-version-200-m9-june-6th-2015">Apache Directory Studio Version 2.0.0-M9 (June 6th 2015)</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="changelog">ChangeLog<a class="headerlink" href="#changelog" title="Permanent link">&para;</a></h1>
+<h2 id="apache-directory-studio-version-200-m9-june-6th-2015">Apache Directory Studio Version 2.0.0-M9 (June 6th 2015)<a class="headerlink" href="#apache-directory-studio-version-200-m9-june-6th-2015" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-815">DIRSTUDIO-815</a> - Tiny translation error [DE]</li>
@@ -231,7 +242,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-1025">DIRSTUDIO-1025</a> - Cleanup after Tycho Migration</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-version-200-m8-july-4th-2013">Apache Directory Studio Version 2.0.0-M8 (July 4th 2013)</h2>
+<h2 id="apache-directory-studio-version-200-m8-july-4th-2013">Apache Directory Studio Version 2.0.0-M8 (July 4th 2013)<a class="headerlink" href="#apache-directory-studio-version-200-m8-july-4th-2013" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-788">DIRSTUDIO-788</a> - Date and Time editor incorrect time format for eDirectory</li>
@@ -259,7 +270,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-925">DIRSTUDIO-925</a> - Add new mandatory and optional attributes introduced for the 'ads-delegatingAuthenticator' object class</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-version-200-m7-may-17th-2013">Apache Directory Studio Version 2.0.0-M7 (May 17th 2013)</h2>
+<h2 id="apache-directory-studio-version-200-m7-may-17th-2013">Apache Directory Studio Version 2.0.0-M7 (May 17th 2013)<a class="headerlink" href="#apache-directory-studio-version-200-m7-may-17th-2013" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-865">DIRSTUDIO-865</a> - NullPointerException thrown when connecting to Domino 8.5.2FP3 LDAP</li>
@@ -287,7 +298,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-901">DIRSTUDIO-901</a> - Add the ability to store connection passwords in a password-protected keystore</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-200-m6-march-8th-2013">Apache Directory Studio 2.0.0-M6 (March 8th 2013)</h2>
+<h2 id="apache-directory-studio-200-m6-march-8th-2013">Apache Directory Studio 2.0.0-M6 (March 8th 2013)<a class="headerlink" href="#apache-directory-studio-200-m6-march-8th-2013" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-861">DIRSTUDIO-861</a> - Errors with DNs containing non-ASCII values on Active Directory</li>
@@ -308,13 +319,13 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-867">DIRSTUDIO-867</a> - References of old projects and packages name 'org.apache.directory.shared' still present in the code</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-200-m5-january-31th-2013">Apache Directory Studio 2.0.0-M5 (January 31th 2013)</h2>
+<h2 id="apache-directory-studio-200-m5-january-31th-2013">Apache Directory Studio 2.0.0-M5 (January 31th 2013)<a class="headerlink" href="#apache-directory-studio-200-m5-january-31th-2013" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-867">DIRSTUDIO-867</a> - References of old projects and packages name 'org.apache.directory.shared' still present in the code</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-200-m4-january-25th-2013">Apache Directory Studio 2.0.0-M4 (January 25th 2013)</h2>
+<h2 id="apache-directory-studio-200-m4-january-25th-2013">Apache Directory Studio 2.0.0-M4 (January 25th 2013)<a class="headerlink" href="#apache-directory-studio-200-m4-january-25th-2013" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-775">DIRSTUDIO-775</a> - Display issues in Image Editor</li>
@@ -365,7 +376,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-839">DIRSTUDIO-839</a> - Update Eclipse dependencies to version 3.8.1</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-200-m3-february-24th-2012">Apache Directory Studio 2.0.0-M3 (February 24th 2012)</h2>
+<h2 id="apache-directory-studio-200-m3-february-24th-2012">Apache Directory Studio 2.0.0-M3 (February 24th 2012)<a class="headerlink" href="#apache-directory-studio-200-m3-february-24th-2012" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-764">DIRSTUDIO-764</a> - Image Editor does not work correctly</li>
@@ -396,7 +407,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-821">DIRSTUDIO-821</a> - Where to get the public certificate used to sign the JAR of DS 1.5.3?</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-200-m2-january-27th-2012">Apache Directory Studio 2.0.0-M2 (January 27th 2012)</h2>
+<h2 id="apache-directory-studio-200-m2-january-27th-2012">Apache Directory Studio 2.0.0-M2 (January 27th 2012)<a class="headerlink" href="#apache-directory-studio-200-m2-january-27th-2012" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-630">DIRSTUDIO-630</a> - Importing a Schema project twice shouldn't be possible</li>
@@ -407,7 +418,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-763">DIRSTUDIO-763</a> - Typo in some English error messages ('occured' instead of 'occurred')</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-200-m1-january-11th-2012">Apache Directory Studio 2.0.0-M1 (January 11th 2012)</h2>
+<h2 id="apache-directory-studio-200-m1-january-11th-2012">Apache Directory Studio 2.0.0-M1 (January 11th 2012)<a class="headerlink" href="#apache-directory-studio-200-m1-january-11th-2012" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-301">DIRSTUDIO-301</a> - Intermittant ClassCastException from dom4j.DocumentFactory.getInstance()</li>
@@ -474,7 +485,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-757">DIRSTUDIO-757</a> - Update all features with the new 'library' plugins</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-153-march-30th-2010">Apache Directory Studio 1.5.3 (March 30th 2010)</h2>
+<h2 id="apache-directory-studio-153-march-30th-2010">Apache Directory Studio 1.5.3 (March 30th 2010)<a class="headerlink" href="#apache-directory-studio-153-march-30th-2010" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-424">DIRSTUDIO-424</a> - Canceling a search gives an error sometimes</li>
@@ -516,7 +527,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-641">DIRSTUDIO-641</a> - Integrate Apache DS version 1.5.6 in the Apache DS plugin</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-152-december-14th-2009">Apache Directory Studio 1.5.2 (December 14th 2009)</h2>
+<h2 id="apache-directory-studio-152-december-14th-2009">Apache Directory Studio 1.5.2 (December 14th 2009)<a class="headerlink" href="#apache-directory-studio-152-december-14th-2009" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-601">DIRSTUDIO-601</a> - The 'Perform Search/Search Again' button in the Search Result Editor does not work correctly</li>
@@ -528,7 +539,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-605">DIRSTUDIO-605</a> - Update the help content of the configuration editor for version 1.5.5 of Apache DS</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-151-december-2nd-2009">Apache Directory Studio 1.5.1 (December 2nd 2009)</h2>
+<h2 id="apache-directory-studio-151-december-2nd-2009">Apache Directory Studio 1.5.1 (December 2nd 2009)<a class="headerlink" href="#apache-directory-studio-151-december-2nd-2009" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-576">DIRSTUDIO-576</a> - Context menu not shown after a right-click on a non-cached entry</li>
@@ -550,7 +561,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-595">DIRSTUDIO-595</a> - The icon of the entry in the 'Outline' view should be the same as the one in the 'LDAP Browser' view</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-150-november-8th-2009">Apache Directory Studio 1.5.0 (November 8th 2009)</h2>
+<h2 id="apache-directory-studio-150-november-8th-2009">Apache Directory Studio 1.5.0 (November 8th 2009)<a class="headerlink" href="#apache-directory-studio-150-november-8th-2009" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-282">DIRSTUDIO-282</a> - Save failed: null, when adding an attribute to a class, if attribute is also open in gui</li>
@@ -660,7 +671,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-167">DIRSTUDIO-167</a> - Show custom icons for various kinds of schema elements while browsing schema data</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-140-april-10th-2009">Apache Directory Studio 1.4.0 (April 10th 2009)</h2>
+<h2 id="apache-directory-studio-140-april-10th-2009">Apache Directory Studio 1.4.0 (April 10th 2009)<a class="headerlink" href="#apache-directory-studio-140-april-10th-2009" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-373">DIRSTUDIO-373</a> - Can't delete a tagged attribute if the non tagged attribute belong to the DN</li>
@@ -717,7 +728,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-439">DIRSTUDIO-439</a> - Ldif importer should be case-insensitive in the changeType attribute</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-130-november-24th-2008">Apache Directory Studio 1.3.0 (November 24th 2008)</h2>
+<h2 id="apache-directory-studio-130-november-24th-2008">Apache Directory Studio 1.3.0 (November 24th 2008)<a class="headerlink" href="#apache-directory-studio-130-november-24th-2008" title="Permanent link">&para;</a></h2>
 <p><strong>Sub-task</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-398">DIRSTUDIO-398</a> - Improve the DSML decorated classes by adding an empty constructor and linking the methods of the underlying ldapmessage</li>
@@ -781,7 +792,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-376">DIRSTUDIO-376</a> - Move to the latest Eclipse 3.4 dependencies</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-120-august-19th-2008">Apache Directory Studio 1.2.0 (August 19th 2008)</h2>
+<h2 id="apache-directory-studio-120-august-19th-2008">Apache Directory Studio 1.2.0 (August 19th 2008)<a class="headerlink" href="#apache-directory-studio-120-august-19th-2008" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-89">DIRSTUDIO-89</a> - Entry painted even though not created in server</li>
@@ -832,10 +843,10 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-339">DIRSTUDIO-339</a> - Add the 'org.eclipse.ui.carbon' Eclipse plugin to the Mac OS X distribution</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-110-april-8th-2008">Apache Directory Studio 1.1.0 (April 8th 2008)</h2>
+<h2 id="apache-directory-studio-110-april-8th-2008">Apache Directory Studio 1.1.0 (April 8th 2008)<a class="headerlink" href="#apache-directory-studio-110-april-8th-2008" title="Permanent link">&para;</a></h2>
 <p>See changelog of Apache Directory Studio 1.1.0 RC and Apache Directory Studio 1.1.0 RC2</p>
 <hr />
-<h2 id="apache-directory-studio-110-rc2-march-4th-2008">Apache Directory Studio 1.1.0 RC2 (March 4th 2008)</h2>
+<h2 id="apache-directory-studio-110-rc2-march-4th-2008">Apache Directory Studio 1.1.0 RC2 (March 4th 2008)<a class="headerlink" href="#apache-directory-studio-110-rc2-march-4th-2008" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-286">DIRSTUDIO-286</a> - Update Site is not working, missing dependencies in ldifeditor, ldapbrower and schemaeditor feature</li>
@@ -850,7 +861,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-280">DIRSTUDIO-280</a> - Remove remaining unwanted contributions from Eclipse</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-110-rc-february-20th-2008">Apache Directory Studio 1.1.0 RC (February 20th 2008)</h2>
+<h2 id="apache-directory-studio-110-rc-february-20th-2008">Apache Directory Studio 1.1.0 RC (February 20th 2008)<a class="headerlink" href="#apache-directory-studio-110-rc-february-20th-2008" title="Permanent link">&para;</a></h2>
 <p><strong>Sub-task</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-142">DIRSTUDIO-142</a> - Add SASL authentication</li>
@@ -946,7 +957,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-265">DIRSTUDIO-265</a> - Migrate our build system from Ant+Ivy to Maven</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-101-september-18th-2007">Apache Directory Studio 1.0.1 (September 18th 2007)</h2>
+<h2 id="apache-directory-studio-101-september-18th-2007">Apache Directory Studio 1.0.1 (September 18th 2007)<a class="headerlink" href="#apache-directory-studio-101-september-18th-2007" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-162">DIRSTUDIO-162</a> - Delete old RDN on rename has no effect</li>
@@ -965,7 +976,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-188">DIRSTUDIO-188</a> - Move LDIF Editor help to its own help plugin</li>
 </ul>
 <hr />
-<h2 id="apache-directory-studio-100-september-4th-2007">Apache Directory Studio 1.0.0 (September 4th 2007)</h2>
+<h2 id="apache-directory-studio-100-september-4th-2007">Apache Directory Studio 1.0.0 (September 4th 2007)<a class="headerlink" href="#apache-directory-studio-100-september-4th-2007" title="Permanent link">&para;</a></h2>
 <p><strong>Sub-task</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-131">DIRSTUDIO-131</a> - Rename package names and plugin IDs for ldap browser plugins and features</li>
@@ -1025,14 +1036,14 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-100">DIRSTUDIO-100</a> - Interface IRootDSE does not sufficiently define return values of methods</li>
 </ul>
 <hr />
-<h2 id="apache-ldap-studio-081-july-24th-2007">Apache LDAP Studio 0.8.1 (July 24th 2007)</h2>
+<h2 id="apache-ldap-studio-081-july-24th-2007">Apache LDAP Studio 0.8.1 (July 24th 2007)<a class="headerlink" href="#apache-ldap-studio-081-july-24th-2007" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-80">DIRSTUDIO-80</a> - LDAP Studio does not work on x86_64</li>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-144">DIRSTUDIO-144</a> - Unable to install plugins from updatesite on x86_64 architecture</li>
 </ul>
 <hr />
-<h2 id="apache-ldap-studio-080-may-4th-2007">Apache LDAP Studio 0.8.0 (May 4th 2007)</h2>
+<h2 id="apache-ldap-studio-080-may-4th-2007">Apache LDAP Studio 0.8.0 (May 4th 2007)<a class="headerlink" href="#apache-ldap-studio-080-may-4th-2007" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-71">DIRSTUDIO-71</a> - LDAP Studio installer creates bad shortcuts</li>
@@ -1055,7 +1066,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-91">DIRSTUDIO-91</a> - Add a new plugin for handling the Apache DS server configuration file</li>
 </ul>
 <hr />
-<h2 id="apache-ldap-studio-070-april-6th-2007">Apache LDAP Studio 0.7.0 (April 6th 2007)</h2>
+<h2 id="apache-ldap-studio-070-april-6th-2007">Apache LDAP Studio 0.7.0 (April 6th 2007)<a class="headerlink" href="#apache-ldap-studio-070-april-6th-2007" title="Permanent link">&para;</a></h2>
 <p><strong>Bug</strong></p>
 <ul>
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-1">DIRSTUDIO-1</a> - DSML Parser does not throw an exception when it doesn't find a requestID attribute when processing=parallel and responseOrder=unordered</li>
@@ -1090,7 +1101,7 @@
 <li><a href="https://issues.apache.org/jira/browse/DIRSTUDIO-41">DIRSTUDIO-41</a> - Add an Overview page on the Schema Editor that displays all ATs and OCs of the schema </li>
 </ul>
 <hr />
-<h2 id="apache-ldap-studio-060-february-13th-2007">Apache LDAP Studio 0.6.0 (February 13th 2007)</h2>
+<h2 id="apache-ldap-studio-060-february-13th-2007">Apache LDAP Studio 0.6.0 (February 13th 2007)<a class="headerlink" href="#apache-ldap-studio-060-february-13th-2007" title="Permanent link">&para;</a></h2>
 <p>Initial Release.</p>
 
 

Modified: websites/staging/directory/trunk/content/studio/developers-guide.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/developers-guide.html (original)
+++ websites/staging/directory/trunk/content/studio/developers-guide.html Sun Jul  5 22:34:35 2015
@@ -151,22 +151,265 @@
 
 
 
-<h1 id="developers-guide">Developer's Guide</h1>
-<p>This is a simple guide to various Apache Directory Studio resources to help developers get going.</p>
-<h2 id="source-repository">Source Repository</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="developers-guide">Developer's Guide<a class="headerlink" href="#developers-guide" title="Permanent link">&para;</a></h1>
+<p>This is a simple guide to various Apache Directory Studio resources to help developers get going. MThis guide can be found in the <a href="https://svn.apache.org/repos/asf/directory/studio/trunk/README.md">README</a> file at the top level of the source tree.</p>
+<h2 id="source-repository">Source Repository<a class="headerlink" href="#source-repository" title="Permanent link">&para;</a></h2>
 <p>The <a href="source-repository.html">Source repository</a> page describes source code location and organization.</p>
-<h2 id="build">Build</h2>
+<h2 id="build">Build<a class="headerlink" href="#build" title="Permanent link">&para;</a></h2>
 <p>The <a href="https://svn.apache.org/repos/asf/directory/studio/trunk/README.md">README</a> describes how to build from source.
 Also on <a href="https://github.com/apache/directory-studio#build-from-command-line">Github</a>. </p>
-<h2 id="setup-eclipse">Setup Eclipse</h2>
+<h3 id="prerequisties">Prerequisties<a class="headerlink" href="#prerequisties" title="Permanent link">&para;</a></h3>
+<ul>
+<li>JDK 7 or newer</li>
+<li>Maven 3 or newer</li>
+<li>Sufficient heap space for Maven: <code>export MAVEN_OPTS="-Xmx512m"</code></li>
+<li>FIXME: Windows users have to replace the repository location <code>file://${basedir}/target/repository</code> in <code>eclipse-trgt-platform/template/org.apache.directory.studio.eclipse-trgt-platform.template</code> with the actual path, e.g. <code>file:///C:/Development/studio/eclipse-trgt-platform/target/repository</code></li>
+</ul>
+<h3 id="building">building<a class="headerlink" href="#building" title="Permanent link">&para;</a></h3>
+<p>You can use either of those two methods to build the project :</p>
+<ul>
+<li>Do it manually</li>
+</ul>
+<p>Build the 'Eclipse Target Platform' and generate MANIFEST.MF files first</p>
+<div class="codehilite"><pre><span class="n">mvn</span> <span class="o">-</span><span class="n">f</span> <span class="n">pom</span><span class="o">-</span><span class="n">first</span><span class="p">.</span><span class="n">xml</span> <span class="n">clean</span> <span class="n">install</span>
+</pre></div>
+
+
+<p>Build the main eclipse artifacts using Tycho</p>
+<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span>
+</pre></div>
+
+
+<ul>
+<li>Use the script  (which runs the two previous commands)</li>
+</ul>
+<p>On Linux / Mac OS X :</p>
+<div class="codehilite"><pre>$ <span class="o">./</span><span class="n">build</span><span class="p">.</span><span class="n">sh</span>
+</pre></div>
+
+
+<p>or on Windows :</p>
+<div class="codehilite"><pre><span class="o">&gt;</span> <span class="n">build</span><span class="p">.</span><span class="n">bat</span>
+</pre></div>
+
+
+<h3 id="tests">Tests<a class="headerlink" href="#tests" title="Permanent link">&para;</a></h3>
+<ul>
+<li>Unit tests included in src/test/java of each plugin are executed automatically and run in 'test' phase</li>
+<li>Core integration tests in tests/test.integration.core are executed automatically and run in 'integration-test' phase</li>
+<li>SWTBot based UI integration tests in tests/test.integration.ui are disabled by default. They can be enabled with -Denable-ui-tests. A failing test generates a screenshot. To not block the developer computer they can run within a virtual framebuffer:<div class="codehilite"><pre><span class="n">export</span> <span class="n">DISPLAY</span><span class="p">=:</span>99
+<span class="n">Xvfb</span> <span class="p">:</span>99 <span class="o">-</span><span class="n">screen</span> 0 1024<span class="n">x768x16</span> <span class="o">&amp;</span>
+</pre></div>
+
+
+</li>
+</ul>
+<h3 id="build-issues">Build issues<a class="headerlink" href="#build-issues" title="Permanent link">&para;</a></h3>
+<p>Tycho doesn't handle snapshot dependencies well. The first time a snapshot dependency is used within the build it is cached in <code>~/.m2/repository/p2</code>. Afterwards any change in the dependency (e.g. ApacheDS or LDAP API) is the considered unless it is deleted from the cache.</p>
+<h2 id="setup-eclipse">Setup Eclipse<a class="headerlink" href="#setup-eclipse" title="Permanent link">&para;</a></h2>
 <p>The <a href="https://svn.apache.org/repos/asf/directory/studio/trunk/README.md">README</a> describes how to setup your Eclipse workspace to work on Apache Directory Studio.
 Also on <a href="https://github.com/apache/directory-studio#setup-eclipse-workspace">Github</a>.</p>
-<h2 id="issue-tracker">Issue Tracker</h2>
+<p>Recommended IDE is 'Eclipse (Luna) for RCP Developers': <a href="http://www.eclipse.org/downloads/packages/eclipse-rcp-and-rap-developers/lunasr2">http://www.eclipse.org/downloads/packages/eclipse-rcp-and-rap-developers/lunasr2</a></p>
+<ol>
+<li>
+<p>Import 'Eclipse Target Platorm' project first</p>
+<ul>
+<li>File -&gt; Import... -&gt; Maven -&gt; Existing Maven Projects</li>
+<li>Choose 'studio/eclipse-trgt-platform' as root directory</li>
+<li>Only this single project is selected</li>
+<li>Finish</li>
+</ul>
+</li>
+<li>
+<p>Initialize target platform</p>
+<ul>
+<li>Open the <code>eclipse-trgt-platform.target</code> file with the 'Target Editor'</li>
+<li>In the top right corner click 'Set as Target Platform'</li>
+</ul>
+</li>
+<li>
+<p>Import the main plugins</p>
+<ul>
+<li>File -&gt; Import... -&gt; Maven -&gt; Existing Maven Projects</li>
+<li>Chosse 'studio' as root directory</li>
+<li>All the plugins are selected</li>
+<li>Finish</li>
+</ul>
+</li>
+</ol>
+<p>During import some Maven plugin connectors need to be installed, accept the installation and restart.</p>
+<h2 id="run">Run<a class="headerlink" href="#run" title="Permanent link">&para;</a></h2>
+<h3 id="from-command-line">From command line<a class="headerlink" href="#from-command-line" title="Permanent link">&para;</a></h3>
+<p>The build produces binaries for all platforms. Archived versions can be found in <code>product/target/products/</code>, unpacked versions can be found below <code>product/target/products/org.apache.directory.studio.product</code></p>
+<h3 id="within-eclipse">Within Eclipse<a class="headerlink" href="#within-eclipse" title="Permanent link">&para;</a></h3>
+<ul>
+<li>Open the product configuration 'org.apache.directory.studio.product' with the Product Configuration Editor</li>
+<li>Click the link 'Launch an Eclipse application'</li>
+</ul>
+<h2 id="issue-tracker">Issue Tracker<a class="headerlink" href="#issue-tracker" title="Permanent link">&para;</a></h2>
 <p><a href="https://issues.apache.org/jira/browse/DIRSTUDIO">Jira</a>.</p>
-<h2 id="release">Release</h2>
+<h2 id="release">Release<a class="headerlink" href="#release" title="Permanent link">&para;</a></h2>
 <p>The release process is described within the <a href="https://svn.apache.org/repos/asf/directory/studio/trunk/README.md">README</a>.
 Also on <a href="https://github.com/apache/directory-studio#release">Github</a>.</p>
-<h2 id="internationalization">Internationalization</h2>
+<p>(Attempts, not fully tested yet...)</p>
+<h3 id="release-artifacts">Release artifacts<a class="headerlink" href="#release-artifacts" title="Permanent link">&para;</a></h3>
+<p>We release the following artifacts:</p>
+<ul>
+<li>Source zip (the main artifact we vote on)</li>
+<li>Maven artifacts<ul>
+<li>poms</li>
+<li>plugins: pom, jar, javadoc, src</li>
+<li>features: pom, jar, src</li>
+<li>helps: pom, jar, src</li>
+</ul>
+</li>
+<li>P2 repositories<ul>
+<li>the main features (LDAP Browser, Schema Editor, ApacheDS)</li>
+<li>dependencies</li>
+</ul>
+</li>
+<li>Product archives for<ul>
+<li>Linux GTK 32bit tar.gz</li>
+<li>Linux GTK 64bit tar.gz</li>
+<li>Mac OS X 64bit tar.gz</li>
+<li>Windows 32bit zip</li>
+<li>Windows 64bit zip</li>
+</ul>
+</li>
+<li>Userguides</li>
+</ul>
+<h3 id="preparation">Preparation<a class="headerlink" href="#preparation" title="Permanent link">&para;</a></h3>
+<p>Test the release build: rat check, javadoc and source jar generation, GPG signing, userguide generation</p>
+<div class="codehilite"><pre><span class="n">mvn</span> <span class="o">-</span><span class="n">f</span> <span class="n">pom</span><span class="o">-</span><span class="n">first</span><span class="p">.</span><span class="n">xml</span> <span class="n">clean</span> <span class="n">install</span>
+<span class="n">mvn</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span> <span class="o">-</span><span class="n">Duserguides</span> <span class="n">clean</span> <span class="n">install</span>
+</pre></div>
+
+
+<p>Run UI tests (if possible on all platforms)</p>
+<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span> <span class="o">-</span><span class="n">Denable</span><span class="o">-</span><span class="n">ui</span><span class="o">-</span><span class="n">tests</span>
+</pre></div>
+
+
+<h3 id="release-build-steps">Release build steps<a class="headerlink" href="#release-build-steps" title="Permanent link">&para;</a></h3>
+<p>As Tycho doesn't support the maven-release-plugin the release process is as follows:</p>
+<h4 id="define-release-version">Define release version<a class="headerlink" href="#define-release-version" title="Permanent link">&para;</a></h4>
+<p>We use a release number scheme that suites for both, Maven and Eclipse.</p>
+<div class="codehilite"><pre><span class="o">&lt;</span><span class="n">MAJOR</span><span class="o">&gt;</span><span class="p">.</span><span class="o">&lt;</span><span class="n">MINOR</span><span class="o">&gt;</span><span class="p">.</span><span class="o">&lt;</span><span class="n">PATCH</span><span class="o">&gt;</span><span class="p">.</span><span class="n">v</span><span class="o">&lt;</span><span class="n">YYYYMMDD</span><span class="o">&gt;</span><span class="p">[</span><span class="o">-</span><span class="n">M</span><span class="o">&lt;</span><span class="n">X</span><span class="o">&gt;|</span><span class="n">RC</span><span class="o">&lt;</span><span class="n">X</span><span class="o">&gt;</span><span class="p">]</span>
+</pre></div>
+
+
+<p>Example for milestone version: <code>2.0.0.v20150529-M9</code>. Example for GA version: <code>2.0.1.v20150529</code>.</p>
+<p>Define a variable for later use:</p>
+<div class="codehilite"><pre><span class="n">export</span> <span class="n">VERSION</span><span class="p">=</span>2<span class="p">.</span>0<span class="p">.</span>0<span class="p">.</span><span class="n">v20150529</span><span class="o">-</span><span class="n">M9</span>
+</pre></div>
+
+
+<p>Also create an empty directory used during the release process and store it in a variable:</p>
+<div class="codehilite"><pre><span class="n">export</span> <span class="n">RELEASE_DIR</span><span class="p">=</span>$<span class="p">(</span><span class="n">pwd</span><span class="p">)</span>
+</pre></div>
+
+
+<h4 id="create-and-checkout-branch">Create and checkout branch<a class="headerlink" href="#create-and-checkout-branch" title="Permanent link">&para;</a></h4>
+<div class="codehilite"><pre><span class="n">cd</span> $<span class="n">RELEASE_DIR</span>
+<span class="n">svn</span> <span class="n">copy</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">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">/</span><span class="n">studio</span><span class="o">/</span><span class="n">trunk</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">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">/</span><span class="n">studio</span><span class="o">/</span><span class="n">branches</span>
 <span class="o">/</span>$<span class="n">VERSION</span> <span class="o">-</span><span class="n">m</span> &quot;<span class="n">Prepare</span> <span class="n">release</span> $<span class="n">VERSION</span>&quot;
+<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">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">/</span><span class="n">studio</span><span class="o">/</span><span class="n">branches</span><span class="o">/</span>$<span class="n">VERSION</span> <span class="n">branch</span><span class="o">-</span>$<span class="n">VERSION</span>
+<span class="n">cd</span> <span class="n">branch</span><span class="o">-</span>$<span class="n">VERSION</span>
+</pre></div>
+
+
+<h4 id="set-the-version">Set the version<a class="headerlink" href="#set-the-version" title="Permanent link">&para;</a></h4>
+<div class="codehilite"><pre><span class="nb">find</span> <span class="p">.</span> <span class="o">-</span><span class="n">name</span> <span class="n">pom</span><span class="o">-</span><span class="n">first</span><span class="p">.</span><span class="n">xml</span> <span class="o">|</span> <span class="n">xargs</span> <span class="n">sed</span> <span class="o">-</span><span class="nb">i</span> <span class="s">&#39;s/2.0.0-SNAPSHOT/&#39;</span>$<span class="n">VERSION</span><span class="o">&#39;/</span><span class="s">&#39;</span>
+<span class="s">find . -name pom-first.xml | xargs sed -i &#39;</span><span class="n">s</span><span class="o">/</span>2<span class="p">.</span>0<span class="p">.</span>0<span class="p">.</span><span class="n">qualifier</span><span class="o">/</span><span class="s">&#39;$VERSION&#39;</span><span class="o">/</span><span class="s">&#39;</span>
+<span class="n">mvn</span> <span class="o">-</span><span class="n">f</span> <span class="n">pom</span><span class="o">-</span><span class="n">first</span><span class="p">.</span><span class="n">xml</span> <span class="n">clean</span> <span class="n">install</span>
+<span class="n">mvn</span> <span class="n">org</span><span class="p">.</span><span class="n">eclipse</span><span class="p">.</span><span class="n">tycho</span><span class="p">:</span><span class="n">tycho</span><span class="o">-</span><span class="n">versions</span><span class="o">-</span><span class="n">plugin</span><span class="p">:</span>0<span class="p">.</span>22<span class="p">.</span>0<span class="p">:</span><span class="n">set</span><span class="o">-</span><span class="n">version</span> <span class="o">-</span><span class="n">DnewVersion</span><span class="p">=</span>$<span class="n">VERSION</span>
+</pre></div>
+
+
+<h4 id="commit">Commit<a class="headerlink" href="#commit" title="Permanent link">&para;</a></h4>
+<div class="codehilite"><pre><span class="n">svn</span> <span class="n">commit</span> <span class="o">-</span><span class="n">m</span> &quot;<span class="n">Set</span> <span class="n">version</span> <span class="n">number</span> <span class="k">for</span> <span class="n">release</span> $<span class="n">VERSION</span>&quot;
+</pre></div>
+
+
+<h4 id="create-and-checkout-tag">Create and checkout tag<a class="headerlink" href="#create-and-checkout-tag" title="Permanent link">&para;</a></h4>
+<div class="codehilite"><pre><span class="n">cd</span> $<span class="n">RELEASE_DIR</span>
+<span class="n">svn</span> <span class="n">copy</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">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">/</span><span class="n">studio</span><span class="o">/</span><span class="n">branches</span><span class="o">/</span>$<span class="n">VERSION</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">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">/</span><span class="n">studio</sp
 an><span class="o">/</span><span class="n">tags</span><span class="o">/</span>$<span class="n">VERSION</span> <span class="o">-</span><span class="n">m</span> &quot;<span class="n">Tag</span> <span class="n">release</span> $<span class="n">VERSION</span>&quot;
+<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">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">/</span><span class="n">studio</span><span class="o">/</span><span class="n">tags</span><span class="o">/</span>$<span class="n">VERSION</span> <span class="n">tag</span><span class="o">-</span>$<span class="n">VERSION</span>
+<span class="n">cd</span> <span class="n">tag</span><span class="o">-</span>$<span class="n">VERSION</span>
+</pre></div>
+
+
+<h4 id="build-the-release-and-deploy-to-staging-nexus-repository">Build the release and deploy to staging Nexus repository<a class="headerlink" href="#build-the-release-and-deploy-to-staging-nexus-repository" title="Permanent link">&para;</a></h4>
+<div class="codehilite"><pre><span class="n">mvn</span> <span class="o">-</span><span class="n">f</span> <span class="n">pom</span><span class="o">-</span><span class="n">first</span><span class="p">.</span><span class="n">xml</span> <span class="n">clean</span> <span class="n">install</span>
+<span class="n">mvn</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span> <span class="o">-</span><span class="n">Duserguides</span> <span class="o">-</span><span class="n">DretryFailedDeploymentCount</span><span class="p">=</span>3 <span class="n">clean</span> <span class="n">deploy</span>
+</pre></div>
+
+
+<h4 id="close-the-staging-nexus-repository">Close the staging Nexus repository<a class="headerlink" href="#close-the-staging-nexus-repository" title="Permanent link">&para;</a></h4>
+<p>See <a href="https://repository.apache.org/#stagingRepositories">https://repository.apache.org/#stagingRepositories</a>.</p>
+<h4 id="package-and-sign-distribution-packages">Package and sign distribution packages<a class="headerlink" href="#package-and-sign-distribution-packages" title="Permanent link">&para;</a></h4>
+<p>There is a script that collects and signs all update sites and distribution packages.</p>
+<p>For non-interactive signing with GPG agent define env variable:</p>
+<div class="codehilite"><pre><span class="n">export</span> <span class="n">RELEASE_KEY</span><span class="p">=</span>28686142
+</pre></div>
+
+
+<p>Run the dist script:</p>
+<div class="codehilite"><pre><span class="n">cd</span> <span class="n">dist</span>
+<span class="o">./</span><span class="n">dist</span><span class="p">.</span><span class="n">sh</span>
+</pre></div>
+
+
+<p>Afterwards all distribution packages are located in <code>target</code>.</p>
+<h3 id="call-the-vote">Call the vote<a class="headerlink" href="#call-the-vote" title="Permanent link">&para;</a></h3>
+<p>Upload <code>target/$VERSION</code> to people.apache.org</p>
+<div class="codehilite"><pre><span class="n">scp</span> <span class="o">-</span><span class="n">r</span> <span class="n">target</span><span class="o">/</span>$<span class="n">VERSION</span> <span class="n">people</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="p">:</span><span class="o">~/</span><span class="n">public_html</span><span class="o">/</span>
+</pre></div>
+
+
+<p>and start the vote.</p>
+<h3 id="publish">Publish<a class="headerlink" href="#publish" title="Permanent link">&para;</a></h3>
+<p>After successful vote we can publish the artifacts</p>
+<ul>
+<li>Release artifacts in Nexus</li>
+<li>Commit distribution packages to https://dist.apache.org/repos/dist/release/directory/studio, the content of <code>dist/target</code> can be used as-is.</li>
+</ul>
+<p>Wait 24h for mirror rsync.</p>
+<h4 id="update-site">Update site<a class="headerlink" href="#update-site" title="Permanent link">&para;</a></h4>
+<p>The update site https://svn.apache.org/repos/asf/directory/site/trunk/content/studio/update needs to be updated.</p>
+<p>In the following files</p>
+<ul>
+<li>compositeArtifacts--xml.html</li>
+<li>compositeContent--xml.html</li>
+<li>product/compositeArtifacts--xml.html</li>
+<li>product/compositeContent--xml.html</li>
+</ul>
+<p>change the location path to the new release and also update the <code>p2.timestamp</code> to the current timestamp milliseconds (hint: <code>date +%s000</code>)</p>
+<h4 id="website">Website<a class="headerlink" href="#website" title="Permanent link">&para;</a></h4>
+<p>Update news and download links</p>
+<ul>
+<li>Versions in <code>lib/path.pm</code></li>
+<li>content/studio/changelog.mdtext</li>
+<li>content/studio/news.mdtext</li>
+</ul>
+<h4 id="user-guides">User guides<a class="headerlink" href="#user-guides" title="Permanent link">&para;</a></h4>
+<p>TODO</p>
+<h4 id="cleanup">Cleanup<a class="headerlink" href="#cleanup" title="Permanent link">&para;</a></h4>
+<p>Delete old releases.</p>
+<h2 id="misc-tips-and-tricks">Misc tips and tricks<a class="headerlink" href="#misc-tips-and-tricks" title="Permanent link">&para;</a></h2>
+<p>How to search features, plugins, versions in P2 repo?</p>
+<p><a href="https://stackoverflow.com/questions/10025599/how-to-find-out-which-feature-contains-a-needed-plug-in-on-an-eclipse-download-s">https://stackoverflow.com/questions/10025599/how-to-find-out-which-feature-contains-a-needed-plug-in-on-an-eclipse-download-s</a></p>
+<h2 id="internationalization">Internationalization<a class="headerlink" href="#internationalization" title="Permanent link">&para;</a></h2>
 <p>The <a href="internationalization.html">Internationalization</a> page describes how to enable multi-language support in the GUI (I18n).</p>
 
 

Modified: websites/staging/directory/trunk/content/studio/developers-howtos/developers-howtos.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/developers-howtos/developers-howtos.html (original)
+++ websites/staging/directory/trunk/content/studio/developers-howtos/developers-howtos.html Sun Jul  5 22:34:35 2015
@@ -151,9 +151,20 @@
 
 
 
-<h1 id="studio-developers-howtos">Studio Developers' Howtos</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="studio-developers-howtos">Studio Developers' Howtos<a class="headerlink" href="#studio-developers-howtos" title="Permanent link">&para;</a></h1>
 <p>Theses guides give some insight about how is developped Studio, so that some new comers can jump in at a limited cost (well, sort of...)</p>
-<h2 id="introduction">Introduction</h2>
+<h2 id="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent link">&para;</a></h2>
 <p>Studio is an Eclipse&tm; RCP application, which can also be loaded into an Eclipse&tm; instance. It's a set of plugins :</p>
 <ul>
 <li>a LDAP Browser</li>
@@ -164,10 +175,10 @@
 <li>an OpenDLAP&tm; 2.4 configuration editor</li>
 </ul>
 <p>and various utility plugins.</p>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h2>
 <p>You can check about what is needed to be able to start coding on <a href="../devezlopers-guide.mdtext">the Developers' guide</a>.</p>
 <p>In any case, you need a Java JDK 7, Eclipse Luna-SR2, Maven 3.2.5, subversion 1.8.8. </p>
-<h2 id="howtos">Howtos</h2>
+<h2 id="howtos">Howtos<a class="headerlink" href="#howtos" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="howtos/table-widget.html">1 - Using the TableWidget<E> widget</a></li>
 </ul>

Modified: websites/staging/directory/trunk/content/studio/developers-howtos/howtos/table-widget.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/developers-howtos/howtos/table-widget.html (original)
+++ websites/staging/directory/trunk/content/studio/developers-howtos/howtos/table-widget.html Sun Jul  5 22:34:35 2015
@@ -151,7 +151,18 @@
 
 
 
-<h1 id="table-widget">Table Widget</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="table-widget">Table Widget<a class="headerlink" href="#table-widget" title="Permanent link">&para;</a></h1>
 <p>It's sometime convenient to use a Table which is associated with a list of optionnally ordered elements, with Add/Edit/Delete actions, and up/down actions if the table is ordered. We have such a widget in <em>org.org.apache.directory.studio.common.ui.widgets</em>. </p>
 <p>The Table which will be exposed looks like this :</p>
 <div class="codehilite"><pre><span class="o">+--------------------------------------+</span>
@@ -177,10 +188,10 @@
 <p>Optionally, the <em>Edit</em> button might be disabled. </p>
 <p>Clicking on an element will select it, so that one can delete it.</p>
 <p>Last, not least, double clicking on an element will edit it, if allowed. In this case, a dedicated Dialog will be opened.</p>
-<h2 id="ordered-table">Ordered table</h2>
+<h2 id="ordered-table">Ordered table<a class="headerlink" href="#ordered-table" title="Permanent link">&para;</a></h2>
 <p>Here, we are not talking about the fact that the elements are ordered using some comparator, but the fact that the elements have an associated numeral prefix which is used to order the elements, regardeless of the element's content. This is an OpenLDAP extension, where elements are prefixed with a <em>{n}</em> String, where 'n' is a vlaue between 0 to MAX_INTEGER (but it can also be -1, in one specific case).</p>
 <p>Bottom line, when a table is declared as Ordered, we use this prefix (which is shown) to order the elements in the tbale, otherwise we use the <em>compareTo</em> method.</p>
-<h2 id="the-element-requirements">The Element requirements</h2>
+<h2 id="the-element-requirements">The Element requirements<a class="headerlink" href="#the-element-requirements" title="Permanent link">&para;</a></h2>
 <p>First of all, we have to focus on the elements. There are some requirements that such Objects much fulfill :</p>
 <ul>
 <li>Either the element can be compared and cloned natively (like an Enum)</li>
@@ -194,7 +205,7 @@
 </li>
 </ul>
 <p>The idea is to be able to find an element in the table using the <em>equals()</em> method, to copy an element, and to order the table content.</p>
-<h2 id="how-it-works">How it works</h2>
+<h2 id="how-it-works">How it works<a class="headerlink" href="#how-it-works" title="Permanent link">&para;</a></h2>
 <p>Basically, we assemble 5 different elements :
     * A Table
     * A listener to handle the actions on the table
@@ -202,7 +213,7 @@
     * A Dialog to edit the elements, or to add them
     * A Wrapper to hold the elements that are stored in the Table</p>
 <p>Let see with some examples</p>
-<h3 id="table-with-addeditdelete-no-dialog">Table with Add/Edit/Delete, no dialog</h3>
+<h3 id="table-with-addeditdelete-no-dialog">Table with Add/Edit/Delete, no dialog<a class="headerlink" href="#table-with-addeditdelete-no-dialog" title="Permanent link">&para;</a></h3>
 <p>Internally, we store the data in a <em>List<E></em> where <em>E</em> is the element's type (<em>TableWidget</em> is a generic class). The only thing you need to do when you want to use this widget is to add this code snippet :</p>
 <div class="codehilite"><pre><span class="cm">/** A TableWidget containing some RootDSE elements */</span>
 <span class="n">private</span> <span class="n">TableWidget</span><span class="o">&lt;</span><span class="n">StringValueWrapper</span><span class="o">&gt;</span> <span class="n">rootDseTableWidget</span><span class="p">;</span> 
@@ -222,7 +233,7 @@
 
 <p>Here, we declare a <em>TableWidget</em>, a type of elements (StringValueWrapper), a label provider (used to decorate the elements in the table, if needed).</p>
 <p>Last, not least, you create the widget and set its position in your screen.</p>
-<h3 id="the-element-wrapper">The element wrapper</h3>
+<h3 id="the-element-wrapper">The element wrapper<a class="headerlink" href="#the-element-wrapper" title="Permanent link">&para;</a></h3>
 <p>We need to wrap the element in the table in order to expose a few basic functions :
     * clone
     * hashCode
@@ -364,7 +375,7 @@
 
 
 <p>Of course, your implementation may be way more complex, but all in all, the API contract is the same.</p>
-<h3 id="the-decorator">The Decorator</h3>
+<h3 id="the-decorator">The Decorator<a class="headerlink" href="#the-decorator" title="Permanent link">&para;</a></h3>
 <p>This is just a class that extends the <em>TableDecorator</em> abstract class. The <em>TableDecorator</em> extendss the <em>LabelProvider</em> class and implements the <em>Comparator</em> interface.</p>
 <p>Here is an example :</p>
 <div class="codehilite"><pre><span class="n">public</span> <span class="n">class</span> <span class="n">StringValueDecorator</span> <span class="n">extends</span> <span class="n">TableDecorator</span><span class="o">&lt;</span><span class="n">StringValueWrapper</span><span class="o">&gt;</span>
@@ -443,7 +454,7 @@
 <p>Here, each line in the Table will represent an instance of a <em>WtringValueWrapper</em>, with no image. Would you need to add an image before the text, it's just a matter to return this image in the <em>getImage()</em> method.</p>
 <p>The constructor takes 2 arguments, the second one will be used in the default Dialog we use to create new String values.</p>
 <p>The text is simply constructed using the <em>toString()</em> method, but you may use whatever fits your need.</p>
-<h3 id="the-dialog">The Dialog</h3>
+<h3 id="the-dialog">The Dialog<a class="headerlink" href="#the-dialog" title="Permanent link">&para;</a></h3>
 <p>This is the complex part, which totally depends on what you want to do. In any case, all the User's Dialog will inherit from the <em>AddEditDialog</em> class, which defines some default actions.</p>
 <p>Here is a quick description of this abstract class :</p>
 <div class="codehilite"><pre><span class="n">AddEditDialog</span><span class="o">&lt;</span><span class="n">E</span><span class="o">&gt;</span> <span class="n">extends</span> <span class="n">Dialog</span>
@@ -518,7 +529,7 @@
 
 
 <p>The rendering can be way more complex though.</p>
-<h3 id="actions">Actions</h3>
+<h3 id="actions">Actions<a class="headerlink" href="#actions" title="Permanent link">&para;</a></h3>
 <p>There are two, three, four or five possible actions on this table :
 <em> Add
 </em> Edit (optional)
@@ -526,22 +537,22 @@
 </em> Up (optional)
 * Down (optional)</p>
 <p>Let's see how it works.</p>
-<h4 id="add-action">Add action</h4>
+<h4 id="add-action">Add action<a class="headerlink" href="#add-action" title="Permanent link">&para;</a></h4>
 <p>We will open the Dialog that is provided, and get back a new element which will be exposed in the Table. We also will check that the element is not already present, and if so, no duplicate will be added, except if the table is ordered.</p>
 <p>If the table is not ordered, the newly created element will be injected at the right place in the Table : we use the <em>compareTo</em> method to find the position it as to be added in. If the element already exists, it's not added.</p>
 <p>If the table is ordered, this is a different story :
 <em> there is a selected element : the newly created element is added <em>after</em> the selection, and all the following elements' prefix are incremented.</em> we don't have any selected element : the newly created element is added at the end of the Table, and its prefix is the laset element's prefix, plus one.</p>
-<h4 id="delete-action">Delete action</h4>
+<h4 id="delete-action">Delete action<a class="headerlink" href="#delete-action" title="Permanent link">&para;</a></h4>
 <p>The delete action only works for a selected element.</p>
 <p>If the Table is ordered, we will update the prefix of the elements after the deleted one, decrementing all of them.</p>
-<h4 id="edit-action">Edit action</h4>
+<h4 id="edit-action">Edit action<a class="headerlink" href="#edit-action" title="Permanent link">&para;</a></h4>
 <p>The edition of an element will replace the selected element by its new value. </p>
 <p>If the Table is ordered, the prefix will not be changed. Otherwise, the edited element might be moved to another position, depending on where it fits accordingly to the <em>compareTo</em> method.</p>
-<h4 id="up-action">Up Action</h4>
+<h4 id="up-action">Up Action<a class="headerlink" href="#up-action" title="Permanent link">&para;</a></h4>
 <p>The Up action will move one element up in the table. It's only valid for an ordered Table. Basically, it does nothing more than just exchanging two elements, and sapping their prefix.</p>
-<h4 id="down-action">Down action</h4>
+<h4 id="down-action">Down action<a class="headerlink" href="#down-action" title="Permanent link">&para;</a></h4>
 <p>The Up action will move one element down in the table. It's only valid for an ordered Table. Basically, it does nothing more than just exchanging two elements, and sapping their prefix.</p>
-<h3 id="the-listener">The listener</h3>
+<h3 id="the-listener">The listener<a class="headerlink" href="#the-listener" title="Permanent link">&para;</a></h3>
 <p>Last, not least, we have to add a Listener to react on what happens on the table itself.</p>
 <p>It's all about post-modification actions. In our case, we want to update the underlaying OpenLDAP configuration :</p>
 <div class="codehilite"><pre><span class="n">private</span> <span class="n">WidgetModifyListener</span> <span class="n">rootDseTableListener</span> <span class="p">=</span> <span class="n">new</span> <span class="n">WidgetModifyListener</span><span class="p">()</span>
@@ -562,7 +573,7 @@
 
 
 <p>But it can be hatever fits your need.</p>
-<h2 id="creating-a-table-with-no-edit-button-or-an-ordered-table">Creating a Table with no edit button, or an Ordered table</h2>
+<h2 id="creating-a-table-with-no-edit-button-or-an-ordered-table">Creating a Table with no edit button, or an Ordered table<a class="headerlink" href="#creating-a-table-with-no-edit-button-or-an-ordered-table" title="Permanent link">&para;</a></h2>
 <p>We have seen how to create a Table with an Edit button. Creating teh other Table's flawors is easy :</p>
 <ul>
 <li>With edit : TableWidget.createWidgetWithEdit( Composite, FormToolkit );</li>



Mime
View raw message