You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by el...@apache.org on 2007/09/21 17:10:09 UTC
svn commit: r578163 [2/2] - in /directory/project/trunk: ./
site/src/site/oldxdocs/ site/src/site/xdoc/
site/src/site/xdoc/community/process/ site/src/site/xdoc/community/who/
site/src/site/xdoc/projects/sitedocs/
Modified: directory/project/trunk/site/src/site/xdoc/community/who/mcconnell.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/community/who/mcconnell.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/community/who/mcconnell.xml (original)
+++ directory/project/trunk/site/src/site/xdoc/community/who/mcconnell.xml Fri Sep 21 08:10:08 2007
@@ -1,55 +1,55 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<document>
- <properties>
- <author email="akarasulu@apache.org">Alex Karasulu</author>
- <title>Apache Directory Project: Contributors</title>
- </properties>
- <body>
- <section name="Stephen McConnell">
- <p>(mcconnell at apache dot org)</p>
- <subsection name="Activities">
- <p>
-Responsible for the coordination and management of many international development projects dealing with large-scale collaborative software development. These projects have involved community building, bootstrap financing (venture capital, government programmes, industrial sponsorship and partnerships), financial coordination and adminstration, operations, and technical direction.
- </p>
- <p>
-Technical expertise includes an in-depth knowledge of CORBA core infrastructure, the IDL and PSDL languages, related common services (naming, PSS, Time, Notification, interceptor and activator frameworks). Comprehensive knowledge of component management systems, component lifecycle concepts, container solutions, component assembly strategies, component isolation, and federation mechanisms. Experience with Java, J2EE, Servlet and related development tools.
- </p>
-
- <p>
-Software Engineering and Best Practices experience is derived from the management and coordination of several large projects in the service management area - provided the opportunity to explore different approaches to service management. This has included assessment of the technical, human and social factors that contribute to functional, usable, and maintainable business systems and in-depth work related to Component and Service Oriented Programming (COP and SOP) and the related principals of SOC and IoC.
- </p>
-
- <p>
-Early experience related to advanced research in the area of distributed multi-agent systems served as the foundations business-level application strategies and related peer-to-peer architectures. Responsible for the initiation of several research and development projects in this area, culminating in the OSM development of a peer-to-peer service management platform.
- </p>
- </subsection>
- <subsection name="Projects">
-<p>
-Lead several international projects related to service management and distribution (from advanced research through to practical application trials). The most relevant of these projects are listed in the following table.
-</p>
- <table>
- <tr><th>Subject</th><th>Description</th></tr>
- <tr><td>Open Source Initative</td>
- <td>Originator and lead developer of the <a href="http://avalon.apache.org/merlin">Apache Avalon Merlin</a> component management platform - an advanced solution dealing with auto-assembly, premptive deployment strategies, based on a full model-driven component architecture. Member of the <a href="http://avalon.apache.org/index.html">Avalon PMC</a> and <a href="http://incubator.apache.org/directory/index.html">Apache Directory PMC"</a>. Founding member of the <a href="http://openorb.sourceforge.net/">Community OpenORB Project</a>.</td>
- </tr>
- <tr><td>Interactive Environments for Distributed Process Management</td>
- <td>The development of an interactive environment for business-to-business service management. Project coordinated by OSM SARL. Research aspects undertaken by Imperial College London. Project involved development of architectural approaches to service policy declaration and the establishment of formal standards in the community and collaboration areas under the <a href="http://www.omg.org">OMG</a>.
- </td>
- </tr>
- <tr><td>Cross-Enterprise Digital Product Management</td>
- <td>A Developer Platform capable of auto-generating complex business systems; an Enterprise Platform capable of executing generated business processes. The project involved approximately 50 participants across 13 partner organisations spanning Europe and the United States. Responsibilities included consortium establishment, administration, management and technical lead.</td>
- </tr>
- <tr><td>The Open Software Architecture Forum</td>
- <td>Resolution of a common methodology and architectures for embedded systems dealing with distributed internet based services. The project established a reference architecture for the European Commission OMI Project and completed several demonstrations and proof of concept solutions validating the integration of distributed service management into intelligent devices. Responsibilities covered project direction and technical lead.</td>
- </tr>
- </table>
- </subsection>
- <subsection name="Snapshot">
- <p><img src="images/mcconnell.jpg"/></p>
- </subsection>
- </section>
- </body>
-</document>
-
-
-
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="akarasulu@apache.org">Alex Karasulu</author>
+ <title>Apache Directory Project: Contributors</title>
+ </properties>
+ <body>
+ <section name="Stephen McConnell">
+ <p>(mcconnell at apache dot org)</p>
+ <subsection name="Activities">
+ <p>
+Responsible for the coordination and management of many international development projects dealing with large-scale collaborative software development. These projects have involved community building, bootstrap financing (venture capital, government programmes, industrial sponsorship and partnerships), financial coordination and adminstration, operations, and technical direction.
+ </p>
+ <p>
+Technical expertise includes an in-depth knowledge of CORBA core infrastructure, the IDL and PSDL languages, related common services (naming, PSS, Time, Notification, interceptor and activator frameworks). Comprehensive knowledge of component management systems, component lifecycle concepts, container solutions, component assembly strategies, component isolation, and federation mechanisms. Experience with Java, J2EE, Servlet and related development tools.
+ </p>
+
+ <p>
+Software Engineering and Best Practices experience is derived from the management and coordination of several large projects in the service management area - provided the opportunity to explore different approaches to service management. This has included assessment of the technical, human and social factors that contribute to functional, usable, and maintainable business systems and in-depth work related to Component and Service Oriented Programming (COP and SOP) and the related principals of SOC and IoC.
+ </p>
+
+ <p>
+Early experience related to advanced research in the area of distributed multi-agent systems served as the foundations business-level application strategies and related peer-to-peer architectures. Responsible for the initiation of several research and development projects in this area, culminating in the OSM development of a peer-to-peer service management platform.
+ </p>
+ </subsection>
+ <subsection name="Projects">
+<p>
+Lead several international projects related to service management and distribution (from advanced research through to practical application trials). The most relevant of these projects are listed in the following table.
+</p>
+ <table>
+ <tr><th>Subject</th><th>Description</th></tr>
+ <tr><td>Open Source Initative</td>
+ <td>Originator and lead developer of the <a href="http://avalon.apache.org/merlin">Apache Avalon Merlin</a> component management platform - an advanced solution dealing with auto-assembly, premptive deployment strategies, based on a full model-driven component architecture. Member of the <a href="http://avalon.apache.org/index.html">Avalon PMC</a> and <a href="http://incubator.apache.org/directory/index.html">Apache Directory PMC"</a>. Founding member of the <a href="http://openorb.sourceforge.net/">Community OpenORB Project</a>.</td>
+ </tr>
+ <tr><td>Interactive Environments for Distributed Process Management</td>
+ <td>The development of an interactive environment for business-to-business service management. Project coordinated by OSM SARL. Research aspects undertaken by Imperial College London. Project involved development of architectural approaches to service policy declaration and the establishment of formal standards in the community and collaboration areas under the <a href="http://www.omg.org">OMG</a>.
+ </td>
+ </tr>
+ <tr><td>Cross-Enterprise Digital Product Management</td>
+ <td>A Developer Platform capable of auto-generating complex business systems; an Enterprise Platform capable of executing generated business processes. The project involved approximately 50 participants across 13 partner organisations spanning Europe and the United States. Responsibilities included consortium establishment, administration, management and technical lead.</td>
+ </tr>
+ <tr><td>The Open Software Architecture Forum</td>
+ <td>Resolution of a common methodology and architectures for embedded systems dealing with distributed internet based services. The project established a reference architecture for the European Commission OMI Project and completed several demonstrations and proof of concept solutions validating the integration of distributed service management into intelligent devices. Responsibilities covered project direction and technical lead.</td>
+ </tr>
+ </table>
+ </subsection>
+ <subsection name="Snapshot">
+ <p><img src="images/mcconnell.jpg"/></p>
+ </subsection>
+ </section>
+ </body>
+</document>
+
+
+
Modified: directory/project/trunk/site/src/site/xdoc/community/who/psteitz.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/community/who/psteitz.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/community/who/psteitz.xml (original)
+++ directory/project/trunk/site/src/site/xdoc/community/who/psteitz.xml Fri Sep 21 08:10:08 2007
@@ -7,7 +7,7 @@
<section name="Phil Steitz">
<p>(psteitz at apache dot org)</p>
<p>
- Phil works on Naming.
+ Phil works on Naming.
</p>
<p>
<a href="http://www.apache.org/~psteitz">Phil's Apache home page</a>
Modified: directory/project/trunk/site/src/site/xdoc/community/who/szoerner.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/community/who/szoerner.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/community/who/szoerner.xml (original)
+++ directory/project/trunk/site/src/site/xdoc/community/who/szoerner.xml Fri Sep 21 08:10:08 2007
@@ -21,7 +21,7 @@
<p>
Stefan Zoerner lives with his family near Hamburg, Germany.
He collects ancient postcards and Sun workstations and likes to write IT related articles (about LDAP topics, sometimes).
- In May 2004, Stefan published a German LDAP book for Java developers
+ In May 2004, Stefan published a German LDAP book for Java developers
(<a href="http://www.entwickler-press.de/buecher/ldap/">LDAP fuer Java-Entwickler</a>),
the second edition appeared in November 2005:
</p>
@@ -38,4 +38,4 @@
</section>
</body>
-</document>
\ No newline at end of file
+</document>
Modified: directory/project/trunk/site/src/site/xdoc/community/who/trustin.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/community/who/trustin.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/community/who/trustin.xml (original)
+++ directory/project/trunk/site/src/site/xdoc/community/who/trustin.xml Fri Sep 21 08:10:08 2007
@@ -1,68 +1,68 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<document>
- <properties>
- <author email="trustin@apache.org">Trustin Lee</author>
- <title>Apache Directory Project: Contributors</title>
- </properties>
- <body>
- <section name="Trustin Lee">
- <p>
- (trustin at apache dot org)
- </p>
-
- <p>
- Trustin is a lead developer for the Apache SEDA framework, and he is
- working on MINA (Multipurpose Infrastructure for Network Applications)
- to improve SEDA framework from ground-up.
- </p>
-
- <p>
- Trustin was born in 1980. He started programming with built-in BASIC
- interpreter in MSX mini computer when he was 8 years old. He enjoyed
- game programming and problem solving using assembly language, C, and
- C++. Finally, he wins bronze medal at Korea information olympiad in
- 1998.
- </p>
-
- <p>
- He worked for several companies as a part time worker who
- writes high-performance network server applications and a few web
- applications after he started to major computer science in Yonsei
- university in South Korea. After graduation, he is working for Arreo
- Communications, Inc which is one of the biggest SMS (mobile short
- message service) provider in Korea.
- </p>
-
- <p>
- Trustin spends his free time taking photos with his lovely SLR camera
- and listening to his favorite compact discs (Japanese pop and Jazz).
- </p>
- </section>
- <section name="Background">
- <p>
- Trustin was getting bored implementing tedious legacy protocols. He
- thought he could save himself by creating a generic framework for
- network applications. The name of the framework was 'Netty' and
- it has been improved for a couple of years until java.nio package is
- introduced.
- </p>
-
- <p>
- NIO changed lots of things, and it impacted Netty. New version of
- Netty was named to Netty2 and released as open source. It gave Trustin
- the experience of open source community and made him fascinated by it.
- </p>
-
- <p>
- Enrique Rodriguez was one of the users of Netty2, and he brought great
- fortune to Trustin. He metioned Netty2 when he approached Alex
- Karasulu, who was the lead for the Apache Directory project. Alex was
- developing SEDA framework as a network application framework at that
- time. He proposed Trustin to get the power of both together and make
- the best network application framework available, and the work is in
- progress actively.
- </p>
- </section>
- </body>
-</document>
-
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="trustin@apache.org">Trustin Lee</author>
+ <title>Apache Directory Project: Contributors</title>
+ </properties>
+ <body>
+ <section name="Trustin Lee">
+ <p>
+ (trustin at apache dot org)
+ </p>
+
+ <p>
+ Trustin is a lead developer for the Apache SEDA framework, and he is
+ working on MINA (Multipurpose Infrastructure for Network Applications)
+ to improve SEDA framework from ground-up.
+ </p>
+
+ <p>
+ Trustin was born in 1980. He started programming with built-in BASIC
+ interpreter in MSX mini computer when he was 8 years old. He enjoyed
+ game programming and problem solving using assembly language, C, and
+ C++. Finally, he wins bronze medal at Korea information olympiad in
+ 1998.
+ </p>
+
+ <p>
+ He worked for several companies as a part time worker who
+ writes high-performance network server applications and a few web
+ applications after he started to major computer science in Yonsei
+ university in South Korea. After graduation, he is working for Arreo
+ Communications, Inc which is one of the biggest SMS (mobile short
+ message service) provider in Korea.
+ </p>
+
+ <p>
+ Trustin spends his free time taking photos with his lovely SLR camera
+ and listening to his favorite compact discs (Japanese pop and Jazz).
+ </p>
+ </section>
+ <section name="Background">
+ <p>
+ Trustin was getting bored implementing tedious legacy protocols. He
+ thought he could save himself by creating a generic framework for
+ network applications. The name of the framework was 'Netty' and
+ it has been improved for a couple of years until java.nio package is
+ introduced.
+ </p>
+
+ <p>
+ NIO changed lots of things, and it impacted Netty. New version of
+ Netty was named to Netty2 and released as open source. It gave Trustin
+ the experience of open source community and made him fascinated by it.
+ </p>
+
+ <p>
+ Enrique Rodriguez was one of the users of Netty2, and he brought great
+ fortune to Trustin. He metioned Netty2 when he approached Alex
+ Karasulu, who was the lead for the Apache Directory project. Alex was
+ developing SEDA framework as a network application framework at that
+ time. He proposed Trustin to get the power of both together and make
+ the best network application framework available, and the work is in
+ progress actively.
+ </p>
+ </section>
+ </body>
+</document>
+
Modified: directory/project/trunk/site/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/index.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/index.xml (original)
+++ directory/project/trunk/site/src/site/xdoc/index.xml Fri Sep 21 08:10:08 2007
@@ -1,63 +1,63 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<document>
- <properties>
- <author email="akarasulu@apache.org">Alex Karasulu</author>
- <title>Welcome !</title>
- <description>The Apache Directory Project aims to produce a high performance and production quality LDAP server written in Java.</description>
- </properties>
- <body>
-
- <section name="News">
- <ul>
- <li><b><a href="http://www.opengroup.org/openbrand/register/brand3527.htm">ApacheDS 1.0 has been certified by the Open Group as an LDAPv3 compatible server!</a></b></li>
- <li><b><a href="subprojects/apacheds/releases.html">ApacheDS 1.0 is out!</a></b></li>
- </ul>
- </section>
- <section name="What is it?">
- <p>
- Before going into all the details here's what the Apache Directory
- Server looks like from an architectural perspective.
- </p>
-
- <map name="directory">
- <area shape="rect" alt="Network Layer" href="subprojects/mina/index.html" target="subprojects/mina/index.html" title="Network Layer" coords="39,155,603,175" />
- <area shape="rect" alt="Protocol Providers" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="Protocol Providers" coords="44,175,595,207" />
- <area shape="rect" alt="Apache Directory Server Core" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="Apache Directory Server Core" coords="209,277,612,443" />
- <area shape="rect" alt="Kerberos Provider" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="Kerberos Provider" coords="457,210,530,225" />
- <area shape="rect" alt="LDAP Provider" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="LDAP Provider" coords="374,210,448,225"/>
- <area shape="rect" alt="DNS Provider" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="DNS Provider" coords="209,210,283,224" />
- <area shape="rect" alt="DHCP Provider" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="DHCP Provider" coords="128,210,202,225" />
- <area shape="rect" alt="NTP Provider" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="NTP Provider" coords="44,209,118,224" />
-</map>
-<img usemap="directory" src="images/50k-ft-architecture.png"/>
- </section>
- <section name="Our Vision">
- <p>
- Our primary vision (others also outlined below) is to build an
- enterprise directory server platform (and its components) where
- other Internet services snap in to store their data within the
- directory so they may be managed using LDAP. From the image
- above you'll see the architecture is designed so services besides
- LDAP like DNS, DHCP, SLP and Kerberos will snap in. Other services
- like UDDI can also be implemented and snapped in. These services
- will use a common networking layer and each can be toggled on and
- off according to the needs of the environment. apseda, mina, or
- sedang are various frameworks used for the common network layer.
- These services share the common network layer and back their data
- within the Apache Directory Server's backing stores without any
- network latency or going through the LDAP line protocol. NTP btw
- is the only exception and it's there to remedy the need for time
- sync for replication and other time sensitive protocols like kerberos.
- Its implementation here is intended to prevent any dependency on
- external infrastructure.
- </p>
-
- <p>
- Other aspects to our vision include becoming the JNDI goto project and
- also becoming the one stop shop for all directory and naming concerns
- here at the ASF. These concerns may be outside of the scope of JNDI
- or may not even fall under Java.
- </p>
- </section>
- </body>
-</document>
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="akarasulu@apache.org">Alex Karasulu</author>
+ <title>Welcome !</title>
+ <description>The Apache Directory Project aims to produce a high performance and production quality LDAP server written in Java.</description>
+ </properties>
+ <body>
+
+ <section name="News">
+ <ul>
+ <li><b><a href="http://www.opengroup.org/openbrand/register/brand3527.htm">ApacheDS 1.0 has been certified by the Open Group as an LDAPv3 compatible server!</a></b></li>
+ <li><b><a href="subprojects/apacheds/releases.html">ApacheDS 1.0 is out!</a></b></li>
+ </ul>
+ </section>
+ <section name="What is it?">
+ <p>
+ Before going into all the details here's what the Apache Directory
+ Server looks like from an architectural perspective.
+ </p>
+
+ <map name="directory">
+ <area shape="rect" alt="Network Layer" href="subprojects/mina/index.html" target="subprojects/mina/index.html" title="Network Layer" coords="39,155,603,175" />
+ <area shape="rect" alt="Protocol Providers" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="Protocol Providers" coords="44,175,595,207" />
+ <area shape="rect" alt="Apache Directory Server Core" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="Apache Directory Server Core" coords="209,277,612,443" />
+ <area shape="rect" alt="Kerberos Provider" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="Kerberos Provider" coords="457,210,530,225" />
+ <area shape="rect" alt="LDAP Provider" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="LDAP Provider" coords="374,210,448,225"/>
+ <area shape="rect" alt="DNS Provider" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="DNS Provider" coords="209,210,283,224" />
+ <area shape="rect" alt="DHCP Provider" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="DHCP Provider" coords="128,210,202,225" />
+ <area shape="rect" alt="NTP Provider" href="subprojects/apacheds/subsubprojects/index.html" target="subprojects/apacheds/subsubprojects/index.html" title="NTP Provider" coords="44,209,118,224" />
+</map>
+<img usemap="directory" src="images/50k-ft-architecture.png"/>
+ </section>
+ <section name="Our Vision">
+ <p>
+ Our primary vision (others also outlined below) is to build an
+ enterprise directory server platform (and its components) where
+ other Internet services snap in to store their data within the
+ directory so they may be managed using LDAP. From the image
+ above you'll see the architecture is designed so services besides
+ LDAP like DNS, DHCP, SLP and Kerberos will snap in. Other services
+ like UDDI can also be implemented and snapped in. These services
+ will use a common networking layer and each can be toggled on and
+ off according to the needs of the environment. apseda, mina, or
+ sedang are various frameworks used for the common network layer.
+ These services share the common network layer and back their data
+ within the Apache Directory Server's backing stores without any
+ network latency or going through the LDAP line protocol. NTP btw
+ is the only exception and it's there to remedy the need for time
+ sync for replication and other time sensitive protocols like kerberos.
+ Its implementation here is intended to prevent any dependency on
+ external infrastructure.
+ </p>
+
+ <p>
+ Other aspects to our vision include becoming the JNDI goto project and
+ also becoming the one stop shop for all directory and naming concerns
+ here at the ASF. These concerns may be outside of the scope of JNDI
+ or may not even fall under Java.
+ </p>
+ </section>
+ </body>
+</document>
Modified: directory/project/trunk/site/src/site/xdoc/projects/sitedocs/hyperlink-management.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/projects/sitedocs/hyperlink-management.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/projects/sitedocs/hyperlink-management.xml (original)
+++ directory/project/trunk/site/src/site/xdoc/projects/sitedocs/hyperlink-management.xml Fri Sep 21 08:10:08 2007
@@ -1,133 +1,133 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<document>
- <properties>
- <author email="akarasulu@apache.org">Alex Karasulu</author>
- <title>Apache Directory Project: </title>
- </properties>
-
- <body>
- <section name="Links Howto">
- <p>
- All links to documents within the same subproject are relative to that
- subproject. Links to resources outside the subproject must take into
- account the relative position of the target directory the subproject's
- generated content is copied into.
- </p>
-
- <p>
- For example the 'directory' link in the sitedocs project is simply
- '/index.html'. The same 'directory' line in the Eve subproject will
- be '../../index.html'. This is because the Eve project's generated
- content ultimately resides two directories deep with the sitedocs
- project's document root here: './subprojects/eve'. It takes a
- '../../' to get to the index.html that is the home page for the TLP
- site.
- </p>
-
- <p>
- Links to Apache, Directory, Eve, LDAP, Naming, Janus, Snickers and
- Sitedocs must be maintained by all subprojects to keep the overall
- site consistant.
- </p>
- </section>
-
- <section name="Navigations">
- <p>
- Maintaining a consistant look and feel means perserving the top level
- site's menus. To do this you'll need to work with the same navigation
- and this requires the following navigation.xml template:
- </p>
-
- <source>
-<?xml version="1.0" encoding="UTF-8"?>
-
-<project>
-
- <title>Apache Directory Project</title>
-
- <body>
-
- <links>
- <item name="Apache" href="http://apache.org/"/>
- <item name="Directory" href="../../index.html"/>
- <item name="Server" href="/index.html"/>
- <item name="LDAP" href="../ldap/index.html"/>
- <item name="Naming" href="../naming/index.html"/>
- <item name="AuthX" href="../authx/index.html"/>
- <item name="ASN1" href="../asn1/index.html"/>
- <item name="Sitedocs" href="../sitedocs/index.html"/>
- </links>
-
- <menu name="About Directory">
- <item name="Overview" href="../../index.html"/>
- <item name="Community" href="../../community/index.html"/>
- <item name="Latest News" href="../../news.html"/>
- <item name="Subprojects" href="../../subprojects/index.html">
- <item name="Server" href="/index.html"/>
- <item name="LDAP" href="../ldap/index.html"/>
- <item name="AuthX" href="../authx/index.html"/>
- <item name="Naming" href="../naming/index.html"/>
- <item name="ASN1" href="../asn1/index.html"/>
- <item name="Sitedocs" href="../sitedocs/index.html"/>
- </item>
- <item name="Documentation" href="../../doc/index.html"/>
- </menu>
-
- <menu name="Resources">
- <item name="IRC" href="../../irc.html"/>
- <item name="Jira" href=
- "http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10400"/>
- <item name="Wiki" href="http://wiki.apache.org/directory"/>
- <item name="Lists" href="../../mailing-lists.html"/>
- <item name="License" href="../../license.html"/>
- <item name="Sandbox" href="../../sandbox/index.html"/>
- <item name="Downloads" href="../../download.cgi"/>
- <item name="Subversion" href="../../svn.html"/>
- <item name="Related Projects" href="../../related/index.html"/>
- </menu>
-
- </body>
-
-</project>
- </source>
-
- <p>
- You can download this navigation template from
- <a href="./nav-template.txt">here</a>. Remember you take this
- template and expand one of the subproject nodes to the number and kind
- of subitems of your choosing by breaking up into a two part tag and
- embedding more items within. For example this is how the Eve
- subproject site navigation is structured:
- </p>
-
- <source>
- <item name="Eve" href="/index.html">
- <item name="Design" href="/design/index.html"/>
- <item name="Features" href="/features.html"/>
- <item name="Backend" href="/backend/index.html"/>
- <item name="Frontend" href="/frontend/index.html"/>
- </item>
- </source>
- </section>
-
- <section name="Links">
- <p>
- Check out the section talking about links. All we do here is let you
- know that you have to keep in mind the distance between the TLP site
- documents and your subproject's site in the final deployed state.
- Basically you have <b>subprojects/[supproject-name]</b> in the way.
- That means two relative levels up to get to TLP resources while the
- resources local to the project are still accessed as relative
- resources.
- </p>
-
- <p>
- If you have questions just take a look at the links section and the
- links in the navigation template above. If you still have questions
- use trial and error until you develope a feel for it. Just generate
- the document and see if it works locally by pointing a browser to it.
- If you still need help post to the list.
- </p>
- </section>
- </body>
-</document>
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="akarasulu@apache.org">Alex Karasulu</author>
+ <title>Apache Directory Project: </title>
+ </properties>
+
+ <body>
+ <section name="Links Howto">
+ <p>
+ All links to documents within the same subproject are relative to that
+ subproject. Links to resources outside the subproject must take into
+ account the relative position of the target directory the subproject's
+ generated content is copied into.
+ </p>
+
+ <p>
+ For example the 'directory' link in the sitedocs project is simply
+ '/index.html'. The same 'directory' line in the Eve subproject will
+ be '../../index.html'. This is because the Eve project's generated
+ content ultimately resides two directories deep with the sitedocs
+ project's document root here: './subprojects/eve'. It takes a
+ '../../' to get to the index.html that is the home page for the TLP
+ site.
+ </p>
+
+ <p>
+ Links to Apache, Directory, Eve, LDAP, Naming, Janus, Snickers and
+ Sitedocs must be maintained by all subprojects to keep the overall
+ site consistant.
+ </p>
+ </section>
+
+ <section name="Navigations">
+ <p>
+ Maintaining a consistant look and feel means perserving the top level
+ site's menus. To do this you'll need to work with the same navigation
+ and this requires the following navigation.xml template:
+ </p>
+
+ <source>
+<?xml version="1.0" encoding="UTF-8"?>
+
+<project>
+
+ <title>Apache Directory Project</title>
+
+ <body>
+
+ <links>
+ <item name="Apache" href="http://apache.org/"/>
+ <item name="Directory" href="../../index.html"/>
+ <item name="Server" href="/index.html"/>
+ <item name="LDAP" href="../ldap/index.html"/>
+ <item name="Naming" href="../naming/index.html"/>
+ <item name="AuthX" href="../authx/index.html"/>
+ <item name="ASN1" href="../asn1/index.html"/>
+ <item name="Sitedocs" href="../sitedocs/index.html"/>
+ </links>
+
+ <menu name="About Directory">
+ <item name="Overview" href="../../index.html"/>
+ <item name="Community" href="../../community/index.html"/>
+ <item name="Latest News" href="../../news.html"/>
+ <item name="Subprojects" href="../../subprojects/index.html">
+ <item name="Server" href="/index.html"/>
+ <item name="LDAP" href="../ldap/index.html"/>
+ <item name="AuthX" href="../authx/index.html"/>
+ <item name="Naming" href="../naming/index.html"/>
+ <item name="ASN1" href="../asn1/index.html"/>
+ <item name="Sitedocs" href="../sitedocs/index.html"/>
+ </item>
+ <item name="Documentation" href="../../doc/index.html"/>
+ </menu>
+
+ <menu name="Resources">
+ <item name="IRC" href="../../irc.html"/>
+ <item name="Jira" href=
+ "http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10400"/>
+ <item name="Wiki" href="http://wiki.apache.org/directory"/>
+ <item name="Lists" href="../../mailing-lists.html"/>
+ <item name="License" href="../../license.html"/>
+ <item name="Sandbox" href="../../sandbox/index.html"/>
+ <item name="Downloads" href="../../download.cgi"/>
+ <item name="Subversion" href="../../svn.html"/>
+ <item name="Related Projects" href="../../related/index.html"/>
+ </menu>
+
+ </body>
+
+</project>
+ </source>
+
+ <p>
+ You can download this navigation template from
+ <a href="./nav-template.txt">here</a>. Remember you take this
+ template and expand one of the subproject nodes to the number and kind
+ of subitems of your choosing by breaking up into a two part tag and
+ embedding more items within. For example this is how the Eve
+ subproject site navigation is structured:
+ </p>
+
+ <source>
+ <item name="Eve" href="/index.html">
+ <item name="Design" href="/design/index.html"/>
+ <item name="Features" href="/features.html"/>
+ <item name="Backend" href="/backend/index.html"/>
+ <item name="Frontend" href="/frontend/index.html"/>
+ </item>
+ </source>
+ </section>
+
+ <section name="Links">
+ <p>
+ Check out the section talking about links. All we do here is let you
+ know that you have to keep in mind the distance between the TLP site
+ documents and your subproject's site in the final deployed state.
+ Basically you have <b>subprojects/[supproject-name]</b> in the way.
+ That means two relative levels up to get to TLP resources while the
+ resources local to the project are still accessed as relative
+ resources.
+ </p>
+
+ <p>
+ If you have questions just take a look at the links section and the
+ links in the navigation template above. If you still have questions
+ use trial and error until you develope a feel for it. Just generate
+ the document and see if it works locally by pointing a browser to it.
+ If you still need help post to the list.
+ </p>
+ </section>
+ </body>
+</document>
Modified: directory/project/trunk/site/src/site/xdoc/projects/sitedocs/maven-changes.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/projects/sitedocs/maven-changes.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/projects/sitedocs/maven-changes.xml (original)
+++ directory/project/trunk/site/src/site/xdoc/projects/sitedocs/maven-changes.xml Fri Sep 21 08:10:08 2007
@@ -1,197 +1,197 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<document>
- <properties>
- <author email="akarasulu@apache.org">Alex Karasulu</author>
- <title>Apache Directory Project: </title>
- </properties>
-
- <body>
- <section name="Overview">
- <p>
- This project documents what is to be the umbrella website for all
- Directory Project Sub-Projects. There are a few rules and information
- that is needed by Sub-Project developers in order to integrate/plugin
- their Sub-Project documentation with this website.
- </p>
-
- <p>
- We use maven and the xdoc format to manage site documents and site
- generation. The layout for the top level site is managed here in this
- project. This is a subproject area which is where subproject content
- is deposited. In case this does not happen correctly some stubs have
- been left in place of the subproject. Here's where we keep subproject
- xdoc stubs:
- </p>
- <source>
-sitedocs/xdocs/subprjects
- ./server
- ./ldap
- ./authx
- ./naming
- ./asn1
- ./kerberos
- ./sitedocs
- </source>
-
- <p>
- Obviously, rather than use stubs, the sitedocs subproject area will
- contain actual content which this page is part of. These directories
- as mentioned before contain stubs. When the top level site is generated
- the html created is deposited int the target/docs directory of the
- sitedocs project directory here:
- </p>
-
- <source>directory/sitedocs/trunk/sitedocs/target/docs</source>
-
- <p>
- It is the reponsibility of subprojects to generate their own content
- and copy it over to their appropriate directory within the subprojects
- directory. The Eve subproject for example does this using a post goal
- within the maven.xml project like so to copy its site documentation:
- </p>
-
- <source>
- <postGoal name="site">
- <attainGoal name="server:copy-images"/>
- <attainGoal name="subproject:collectdocs"/>
- </postGoal>
-
- <goal name="subproject:collectdocs">
- <copy toDir="../../../sitedocs/trunk/sitedocs/target/docs/subprojects/eve">
- <fileSet dir="${basedir}/target/docs">
- <include name="**"/>
- </fileSet>
- </copy>
- </goal>
- </source>
-
- <p>
- This however is not the only requirement. As we'll see to maintain
- consistancy throughout the site subproject documentation needs to
- manage links, manage the same navigations, set properties in maven
- and its pom.
- </p>
- </section>
-
- <section name="Subproject Integration Howto">
- <p>
- At the present time there are stubs that have been placed
- into the respective directories for the subprojects. So under <b>
- sitedocs/xdocs/subprojects</b> where subproject directories are
- contained a stub <b><em>index.xml</em></b> and <b><em>navigation.xml
- </em></b> will be found.
- </p>
-
- <p>
- We have done this to prevent users from encountering broken links on the
- site. Once you have built your subproject's site and are sure it works
- remove the respective stubs for your subproject. If you do not do so
- your content may be over written by the stubs if someone deploys the
- top level site without generating your subproject's content. So please
- rm these stubs from the repository once your subproject is up.
- </p>
-
- <p>
- Below we point out all the files and changes that need to be made in
- order to make your subproject integrate into the top level site to
- maintain a consistant look and feel.
- </p>
-
- <subsection name="project.properties">
- <p>
- Add this to your maven project.properties at the top level of the
- project:
- </p>
-
- <source>
-maven.xdoc.date=left
-maven.ui.banner.background=#FFFFFF
-maven.xdoc.includeProjectDocumentation=no
-maven.xdoc.poweredby.image=
-maven.xdoc.jsl = file:/${basedir}/../../../sitedocs/trunk/sitedocs/src/etc/site.jsl
- </source>
-
- <p>
- The last property is a relative reference to the
- <b>sitedocs/src/etc/site.jsl</b> file. You can copy this if you want
- into your own directory but I recommend you keep a reference since
- it effects the sense of site continuity and the general look and feel
- that is carried along on every subproject. There is no need to keep
- them the same but it just might look better. Copying the file and
- versioning it in a subproject directory will allow the top and
- subproject sites to diverge.
- </p>
- </subsection>
-
- <subsection name="project.xml">
- <p>
- You have to make a couple of minor changes to the project.xml to make
- the project and banner logos look the same on the TLP site and the
- subproject site. Here's the set of tags and the values they should
- be set to in order to maintain consistancy:
- </p>
-
- <source>
-<name>Apache Directory Project</name>
-<url>http://incubator.apache.org/directory</url>
-<logo>http://incubator.apache.org/directory/images/apache-directory-logo.png</logo>
-
-<organization>
- <name>Apache Incubator</name>
- <url>http://incubator.apache.org</url>
- <logo>http://incubator.apache.org/directory/images/apache-incubator-logo.png</logo>
-</organization>
- </source>
-
- <p>
- The first stanza above should set the alt hints and link for the
- project logo banner in the upper right hand corner using the following
- graphic:
- </p>
-
- <img src="http://incubator.apache.org/directory/images/apache-directory-logo.png"/>
-
- <p>
- The second stanza sets the organization logo which for now is the
- Apache Incubator. The organization logo appears at the upper right
- hand side, links to the incubator's main site and hold's alt hints
- for the incubator. The following graphic will appear for this logo:
- </p>
-
- <img src="http://incubator.apache.org/directory/images/apache-incubator-logo.png"/>
- </subsection>
-
- <subsection name="maven.xml">
- <p>
- Some scripting is required within the maven jelly scripting file for
- your project. As you may already know this maven.xml file sits at
- your projects top level directory along side your project.xml file.
- Here's what you have to add to it:
- </p>
-
- <source>
- <postGoal name="site">
- <attainGoal name="subproject:collectdocs"/>
- </postGoal>
-
- <goal name="subproject:collectdocs">
- <ant:copy toDir="../../../sitedocs/trunk/sitedocs/target/docs/subprojects/[subproject-name]">
- <ant:fileSet dir="${basedir}/target/docs">
- <ant:include name="**"/>
- </ant:fileSet>
- </ant:copy>
- </goal>
- </source>
-
- <p>
- This Jelly code sets up a new goal to execute after the subproject's
- site has been built. It is called <em>subproject:collectdocs</em>.
- Make sure you edit the toDir attribute value on the <ant:copy>
- tag to use your subprojects destination directory. It will copy the
- generated output of your subproject site build under the sitedocs
- directory in the respective position.
- </p>
- </subsection>
- </section>
- </body>
-</document>
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="akarasulu@apache.org">Alex Karasulu</author>
+ <title>Apache Directory Project: </title>
+ </properties>
+
+ <body>
+ <section name="Overview">
+ <p>
+ This project documents what is to be the umbrella website for all
+ Directory Project Sub-Projects. There are a few rules and information
+ that is needed by Sub-Project developers in order to integrate/plugin
+ their Sub-Project documentation with this website.
+ </p>
+
+ <p>
+ We use maven and the xdoc format to manage site documents and site
+ generation. The layout for the top level site is managed here in this
+ project. This is a subproject area which is where subproject content
+ is deposited. In case this does not happen correctly some stubs have
+ been left in place of the subproject. Here's where we keep subproject
+ xdoc stubs:
+ </p>
+ <source>
+sitedocs/xdocs/subprjects
+ ./server
+ ./ldap
+ ./authx
+ ./naming
+ ./asn1
+ ./kerberos
+ ./sitedocs
+ </source>
+
+ <p>
+ Obviously, rather than use stubs, the sitedocs subproject area will
+ contain actual content which this page is part of. These directories
+ as mentioned before contain stubs. When the top level site is generated
+ the html created is deposited int the target/docs directory of the
+ sitedocs project directory here:
+ </p>
+
+ <source>directory/sitedocs/trunk/sitedocs/target/docs</source>
+
+ <p>
+ It is the reponsibility of subprojects to generate their own content
+ and copy it over to their appropriate directory within the subprojects
+ directory. The Eve subproject for example does this using a post goal
+ within the maven.xml project like so to copy its site documentation:
+ </p>
+
+ <source>
+ <postGoal name="site">
+ <attainGoal name="server:copy-images"/>
+ <attainGoal name="subproject:collectdocs"/>
+ </postGoal>
+
+ <goal name="subproject:collectdocs">
+ <copy toDir="../../../sitedocs/trunk/sitedocs/target/docs/subprojects/eve">
+ <fileSet dir="${basedir}/target/docs">
+ <include name="**"/>
+ </fileSet>
+ </copy>
+ </goal>
+ </source>
+
+ <p>
+ This however is not the only requirement. As we'll see to maintain
+ consistancy throughout the site subproject documentation needs to
+ manage links, manage the same navigations, set properties in maven
+ and its pom.
+ </p>
+ </section>
+
+ <section name="Subproject Integration Howto">
+ <p>
+ At the present time there are stubs that have been placed
+ into the respective directories for the subprojects. So under <b>
+ sitedocs/xdocs/subprojects</b> where subproject directories are
+ contained a stub <b><em>index.xml</em></b> and <b><em>navigation.xml
+ </em></b> will be found.
+ </p>
+
+ <p>
+ We have done this to prevent users from encountering broken links on the
+ site. Once you have built your subproject's site and are sure it works
+ remove the respective stubs for your subproject. If you do not do so
+ your content may be over written by the stubs if someone deploys the
+ top level site without generating your subproject's content. So please
+ rm these stubs from the repository once your subproject is up.
+ </p>
+
+ <p>
+ Below we point out all the files and changes that need to be made in
+ order to make your subproject integrate into the top level site to
+ maintain a consistant look and feel.
+ </p>
+
+ <subsection name="project.properties">
+ <p>
+ Add this to your maven project.properties at the top level of the
+ project:
+ </p>
+
+ <source>
+maven.xdoc.date=left
+maven.ui.banner.background=#FFFFFF
+maven.xdoc.includeProjectDocumentation=no
+maven.xdoc.poweredby.image=
+maven.xdoc.jsl = file:/${basedir}/../../../sitedocs/trunk/sitedocs/src/etc/site.jsl
+ </source>
+
+ <p>
+ The last property is a relative reference to the
+ <b>sitedocs/src/etc/site.jsl</b> file. You can copy this if you want
+ into your own directory but I recommend you keep a reference since
+ it effects the sense of site continuity and the general look and feel
+ that is carried along on every subproject. There is no need to keep
+ them the same but it just might look better. Copying the file and
+ versioning it in a subproject directory will allow the top and
+ subproject sites to diverge.
+ </p>
+ </subsection>
+
+ <subsection name="project.xml">
+ <p>
+ You have to make a couple of minor changes to the project.xml to make
+ the project and banner logos look the same on the TLP site and the
+ subproject site. Here's the set of tags and the values they should
+ be set to in order to maintain consistancy:
+ </p>
+
+ <source>
+<name>Apache Directory Project</name>
+<url>http://incubator.apache.org/directory</url>
+<logo>http://incubator.apache.org/directory/images/apache-directory-logo.png</logo>
+
+<organization>
+ <name>Apache Incubator</name>
+ <url>http://incubator.apache.org</url>
+ <logo>http://incubator.apache.org/directory/images/apache-incubator-logo.png</logo>
+</organization>
+ </source>
+
+ <p>
+ The first stanza above should set the alt hints and link for the
+ project logo banner in the upper right hand corner using the following
+ graphic:
+ </p>
+
+ <img src="http://incubator.apache.org/directory/images/apache-directory-logo.png"/>
+
+ <p>
+ The second stanza sets the organization logo which for now is the
+ Apache Incubator. The organization logo appears at the upper right
+ hand side, links to the incubator's main site and hold's alt hints
+ for the incubator. The following graphic will appear for this logo:
+ </p>
+
+ <img src="http://incubator.apache.org/directory/images/apache-incubator-logo.png"/>
+ </subsection>
+
+ <subsection name="maven.xml">
+ <p>
+ Some scripting is required within the maven jelly scripting file for
+ your project. As you may already know this maven.xml file sits at
+ your projects top level directory along side your project.xml file.
+ Here's what you have to add to it:
+ </p>
+
+ <source>
+ <postGoal name="site">
+ <attainGoal name="subproject:collectdocs"/>
+ </postGoal>
+
+ <goal name="subproject:collectdocs">
+ <ant:copy toDir="../../../sitedocs/trunk/sitedocs/target/docs/subprojects/[subproject-name]">
+ <ant:fileSet dir="${basedir}/target/docs">
+ <ant:include name="**"/>
+ </ant:fileSet>
+ </ant:copy>
+ </goal>
+ </source>
+
+ <p>
+ This Jelly code sets up a new goal to execute after the subproject's
+ site has been built. It is called <em>subproject:collectdocs</em>.
+ Make sure you edit the toDir attribute value on the <ant:copy>
+ tag to use your subprojects destination directory. It will copy the
+ generated output of your subproject site build under the sitedocs
+ directory in the respective position.
+ </p>
+ </subsection>
+ </section>
+ </body>
+</document>
Modified: directory/project/trunk/site/src/site/xdoc/projects/sitedocs/nav-template.txt
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/projects/sitedocs/nav-template.txt?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/projects/sitedocs/nav-template.txt (original)
+++ directory/project/trunk/site/src/site/xdoc/projects/sitedocs/nav-template.txt Fri Sep 21 08:10:08 2007
@@ -1,50 +1,50 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<project>
-
- <title>Apache Directory Project</title>
-
- <body>
-
- <links>
- <item name="Apache" href="http://apache.org/"/>
- <item name="Directory" href="../../index.html"/>
- <item name="Eve" href="/index.html"/>
- <item name="LDAP" href="../ldap/index.html"/>
- <item name="Naming" href="../naming/index.html"/>
- <item name="Janus" href="../janus/index.html"/>
- <item name="Snickers" href="../snickers/index.html"/>
- <item name="Sitedocs" href="../sitedocs/index.html"/>
- </links>
-
- <menu name="About Directory">
- <item name="Overview" href="../../index.html"/>
- <item name="Community" href="../../community/index.html"/>
- <item name="Latest News" href="../../news.html"/>
- <item name="Subprojects" href="../../subprojects/index.html">
- <item name="Eve" href="/index.html"/>
- <item name="LDAP" href="../ldap/index.html"/>
- <item name="Janus" href="../janus/index.html"/>
- <item name="Naming" href="../naming/index.html"/>
- <item name="Snickers" href="../snickers/index.html"/>
- <item name="Sitedocs" href="../sitedocs/index.html"/>
- </item>
- <item name="Documentation" href="../../doc/index.html"/>
- </menu>
-
- <menu name="Resources">
- <item name="IRC" href="../../irc.html"/>
- <item name="Jira" href=
- "http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10400"/>
- <item name="Wiki" href="http://wiki.apache.org/directory"/>
- <item name="Lists" href="../../mailing-lists.html"/>
- <item name="License" href="../../license.html"/>
- <item name="Sandbox" href="../../sandbox/index.html"/>
- <item name="Downloads" href="../../download.cgi"/>
- <item name="Subversion" href="../../svn.html"/>
- <item name="Related Projects" href="../../related/index.html"/>
- </menu>
-
- </body>
-
-</project>
+<?xml version="1.0" encoding="UTF-8"?>
+
+<project>
+
+ <title>Apache Directory Project</title>
+
+ <body>
+
+ <links>
+ <item name="Apache" href="http://apache.org/"/>
+ <item name="Directory" href="../../index.html"/>
+ <item name="Eve" href="/index.html"/>
+ <item name="LDAP" href="../ldap/index.html"/>
+ <item name="Naming" href="../naming/index.html"/>
+ <item name="Janus" href="../janus/index.html"/>
+ <item name="Snickers" href="../snickers/index.html"/>
+ <item name="Sitedocs" href="../sitedocs/index.html"/>
+ </links>
+
+ <menu name="About Directory">
+ <item name="Overview" href="../../index.html"/>
+ <item name="Community" href="../../community/index.html"/>
+ <item name="Latest News" href="../../news.html"/>
+ <item name="Subprojects" href="../../subprojects/index.html">
+ <item name="Eve" href="/index.html"/>
+ <item name="LDAP" href="../ldap/index.html"/>
+ <item name="Janus" href="../janus/index.html"/>
+ <item name="Naming" href="../naming/index.html"/>
+ <item name="Snickers" href="../snickers/index.html"/>
+ <item name="Sitedocs" href="../sitedocs/index.html"/>
+ </item>
+ <item name="Documentation" href="../../doc/index.html"/>
+ </menu>
+
+ <menu name="Resources">
+ <item name="IRC" href="../../irc.html"/>
+ <item name="Jira" href=
+ "http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10400"/>
+ <item name="Wiki" href="http://wiki.apache.org/directory"/>
+ <item name="Lists" href="../../mailing-lists.html"/>
+ <item name="License" href="../../license.html"/>
+ <item name="Sandbox" href="../../sandbox/index.html"/>
+ <item name="Downloads" href="../../download.cgi"/>
+ <item name="Subversion" href="../../svn.html"/>
+ <item name="Related Projects" href="../../related/index.html"/>
+ </menu>
+
+ </body>
+
+</project>
Modified: directory/project/trunk/site/src/site/xdoc/projects/sitedocs/sitedoc-deployment.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/projects/sitedocs/sitedoc-deployment.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/projects/sitedocs/sitedoc-deployment.xml (original)
+++ directory/project/trunk/site/src/site/xdoc/projects/sitedocs/sitedoc-deployment.xml Fri Sep 21 08:10:08 2007
@@ -1,109 +1,109 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<document>
- <properties>
- <author email="akarasulu@apache.org">Alex Karasulu</author>
- <title>Apache Directory Project: </title>
- </properties>
-
- <body>
- <section name="Deploying Site and Subprojects">
- <subsection name="Incubator Site">
- <p>
- The entire Apache Incubator site is kept within CVS. This includes
- generated files. There has to be a good Apache Incubator resource
- for this in existance that explains how it is all organized. Until
- I figure that out just follow along.
- </p>
-
- <p>
- Currently as a podling the Directory Project's resources are managed
- under the Apache Incubator. The website is no exception. The
- specific incubator module used is the <b>incubator-directory</b> CVS
- module. I check it out like so:
- </p>
-
- <source>
-cvs -d :ext:akarasulu@cvs.apache.org:/home/cvs co incubator-directory
- </source>
-
- <p>
- This module contains a content directory: <b>www</b>. The final
- content under <b>www</b> is served up by the Apache servers. The
- module's <b>www</b> folder is checked out daily into the following
- directory on minotaur.apache.org:
- <b>/www/incubator.apache.org/directory</b>
- </p>
-
- <p>
- So all we have to do is generate the site out of our subversion
- working directory and copy the Maven generated content into the
- <b>www</b> folder of the CVS working copy for the incubator-directory
- CVS module. That's a mouth full.
- </p>
-
- <p>
- Once the generated content is copied, the changes are committed. Then
- deployers should ssh into minotaur and cd to the
- <b>/www/incubator.apache.org/directory</b> to do an update like so:
- </p>
-
- <source>
-cd /www/incubator.apache.org/directory
-cvs update -d
- </source>
-
- <p>
- Everyone within our team has access to this area. Anyone can deploy
- the entire site or just a part of it this way. It's a pretty neat
- setup and works well.
- </p>
-
- </subsection>
-
- <subsection name="Building Top Level Project Site">
- <p>
- Keep in mind that the subprojects contain their own documentation.
- They hook into the TLP Site. The sitedocs project manages the TLP
- site shell. Any documentation that is not specific to a subproject
- goes here.
- </p>
-
- <p>
- Building the top level project site is really simple. You checkout
- the sitedocs trunk form the subversion repository. Add, delete or
- make changes to the xdocs that reside under the <b>xdocs</b> folder.
- Once the changes are made run:
- </p>
-
- <source>
-maven site
- </source>
-
- <p>
- This will generate the TLP site right under <b>target/docs</b>.
- This does not generate the subproject content. To do this you'll
- have to build the subproject documentation by using the same command
- on the respective subproject. If all subprojects are configured as
- documented here in the subproject integration section above then the
- subproject build should copy the generated subproject documents over
- to the respective <b>target/docs/subprojects/[subproject]</b> output
- folder of the sitedocs module.
- </p>
-
- <p>
- If you're changes are to the TLP only without changes to the
- subprojects then there is no need to build any subproject sites. If
- you want to deploy one or more subproject site changes then go ahead
- and build the subproject site for every subproject module. All the
- results collect under the <b>sitedocs/target/docs</b> folder.
- </p>
-
- <p>
- The contents of the <b>sitedocs/target/docs</b> folder is what is
- copied over into the <b>incubator-directory/www</b> folder and
- committed into CVS.
- </p>
- </subsection>
- </section>
- </body>
-</document>
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="akarasulu@apache.org">Alex Karasulu</author>
+ <title>Apache Directory Project: </title>
+ </properties>
+
+ <body>
+ <section name="Deploying Site and Subprojects">
+ <subsection name="Incubator Site">
+ <p>
+ The entire Apache Incubator site is kept within CVS. This includes
+ generated files. There has to be a good Apache Incubator resource
+ for this in existance that explains how it is all organized. Until
+ I figure that out just follow along.
+ </p>
+
+ <p>
+ Currently as a podling the Directory Project's resources are managed
+ under the Apache Incubator. The website is no exception. The
+ specific incubator module used is the <b>incubator-directory</b> CVS
+ module. I check it out like so:
+ </p>
+
+ <source>
+cvs -d :ext:akarasulu@cvs.apache.org:/home/cvs co incubator-directory
+ </source>
+
+ <p>
+ This module contains a content directory: <b>www</b>. The final
+ content under <b>www</b> is served up by the Apache servers. The
+ module's <b>www</b> folder is checked out daily into the following
+ directory on minotaur.apache.org:
+ <b>/www/incubator.apache.org/directory</b>
+ </p>
+
+ <p>
+ So all we have to do is generate the site out of our subversion
+ working directory and copy the Maven generated content into the
+ <b>www</b> folder of the CVS working copy for the incubator-directory
+ CVS module. That's a mouth full.
+ </p>
+
+ <p>
+ Once the generated content is copied, the changes are committed. Then
+ deployers should ssh into minotaur and cd to the
+ <b>/www/incubator.apache.org/directory</b> to do an update like so:
+ </p>
+
+ <source>
+cd /www/incubator.apache.org/directory
+cvs update -d
+ </source>
+
+ <p>
+ Everyone within our team has access to this area. Anyone can deploy
+ the entire site or just a part of it this way. It's a pretty neat
+ setup and works well.
+ </p>
+
+ </subsection>
+
+ <subsection name="Building Top Level Project Site">
+ <p>
+ Keep in mind that the subprojects contain their own documentation.
+ They hook into the TLP Site. The sitedocs project manages the TLP
+ site shell. Any documentation that is not specific to a subproject
+ goes here.
+ </p>
+
+ <p>
+ Building the top level project site is really simple. You checkout
+ the sitedocs trunk form the subversion repository. Add, delete or
+ make changes to the xdocs that reside under the <b>xdocs</b> folder.
+ Once the changes are made run:
+ </p>
+
+ <source>
+maven site
+ </source>
+
+ <p>
+ This will generate the TLP site right under <b>target/docs</b>.
+ This does not generate the subproject content. To do this you'll
+ have to build the subproject documentation by using the same command
+ on the respective subproject. If all subprojects are configured as
+ documented here in the subproject integration section above then the
+ subproject build should copy the generated subproject documents over
+ to the respective <b>target/docs/subprojects/[subproject]</b> output
+ folder of the sitedocs module.
+ </p>
+
+ <p>
+ If you're changes are to the TLP only without changes to the
+ subprojects then there is no need to build any subproject sites. If
+ you want to deploy one or more subproject site changes then go ahead
+ and build the subproject site for every subproject module. All the
+ results collect under the <b>sitedocs/target/docs</b> folder.
+ </p>
+
+ <p>
+ The contents of the <b>sitedocs/target/docs</b> folder is what is
+ copied over into the <b>incubator-directory/www</b> folder and
+ committed into CVS.
+ </p>
+ </subsection>
+ </section>
+ </body>
+</document>