From 2416f0f66668684be1c4de6e9ed71bbc04f8efdd Mon Sep 17 00:00:00 2001
From: Mark Craig <mark.craig@forgerock.com>
Date: Mon, 16 May 2011 15:33:05 +0000
Subject: [PATCH] Adding machinery for building http://opendj.forgerock.org/ (Note: the French localization still needs to be done. Adding the Maven sample files as a placeholder.
---
opendj3/src/site/fr/apt/format.apt | 602 ++++++++++++++++++
opendj3/src/site/site.xml | 104 +++
opendj3/opendj-docs/pom.xml | 58 +
opendj3/pom.xml | 18
opendj3/src/site/fr/fml/faq.fml | 27
opendj3/src/site/xdoc/news.xml | 47 +
opendj3/src/site/fml/faq.fml | 147 ++++
opendj3/src/site/fr/xdoc/xdoc.xml | 17
opendj3/src/site/fr/apt/index.apt | 17
opendj3/src/site/xdoc/index.xml | 106 +++
opendj3/opendj-docs/src/main/resources/css/coredoc.css | 96 ++
opendj3/src/site/apt/format.apt | 602 ++++++++++++++++++
opendj3/src/site/site_fr.xml | 27
13 files changed, 1,830 insertions(+), 38 deletions(-)
diff --git a/opendj3/opendj-docs/pom.xml b/opendj3/opendj-docs/pom.xml
index 34ec793..30cb7a0 100644
--- a/opendj3/opendj-docs/pom.xml
+++ b/opendj3/opendj-docs/pom.xml
@@ -31,20 +31,11 @@
<name>OpenDJ Core User Documentation</name>
<packaging>pom</packaging>
<description>DocBook XML source for OpenDJ core user documentation. Java API and configuration reference documentation is generated from OpenDJ source code.</description>
- <repositories>
- <repository>
- <id>forgerock-snapshots-repository</id>
- <name>ForgeRock Snapshot Repository</name>
- <url>http://maven.forgerock.org/repo/snapshots</url>
- <releases>
- <enabled>false</enabled>
- </releases>
- </repository>
- </repositories>
<properties>
<docbkx-src>${basedir}/src/docbkx</docbkx-src>
<dbstyle-dir>${basedir}/src/docbkx-stylesheets</dbstyle-dir>
<docbkx-out>${basedir}/target/docbkx</docbkx-out>
+ <site-out>${project.parent.basedir}/target/site</site-out>
</properties>
<build>
<plugins>
@@ -146,23 +137,64 @@
<executions>
<execution>
<id>fix-legalnotice</id>
- <phase>post-site</phase>
+ <phase>site</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
+ <detail>true</detail>
<target>
<!-- TODO: Figure out how to say foreach in ant. -->
- <!-- How do I say pwd in ant or in Maven? -->
<copy file='${env.PWD}/legalnotice.html' todir='${basedir}/target/docbkx/html/admin-guide' />
<copy file='${env.PWD}/legalnotice.html' todir='${basedir}/target/docbkx/html/dev-guide' />
<copy file='${env.PWD}/legalnotice.html' todir='${basedir}/target/docbkx/html/install-guide' />
- <move file='${env.PWD}/legalnotice.html' todir='${basedir}/target/docbkx/html/release-notes' />
+ <move file='${env.PWD}/legalnotice.html' todir='${basedir}/target/docbkx/html/release-notes' />
</target>
</configuration>
</execution>
</executions>
</plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-resources-plugin</artifactId>
+ <executions>
+ <execution>
+ <phase>site</phase>
+ <goals>
+ <goal>copy-resources</goal>
+ </goals>
+ <configuration>
+ <outputDirectory>${site-out}/doc</outputDirectory>
+ <resources>
+ <resource>
+ <directory>${docbkx-out}/epub/admin-guide</directory>
+ <directory>${docbkx-out}/epub/dev-guide</directory>
+ <directory>${docbkx-out}/epub/install-guide</directory>
+ <directory>${docbkx-out}/epub/release-notes</directory>
+ <includes>
+ <include>**/*.epub</include>
+ </includes>
+ </resource>
+ <resource>
+ <directory>${docbkx-out}/html/</directory>
+ </resource>
+ <resource>
+ <directory>${docbkx-out}/pdf</directory>
+ <includes>
+ <include>**/*.pdf</include>
+ </includes>
+ </resource>
+ <resource>
+ <directory>${docbkx-out}/rtf</directory>
+ <includes>
+ <include>**/*.rtf</include>
+ </includes>
+ </resource>
+ </resources>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
</plugins>
</build>
<parent>
diff --git a/opendj3/opendj-docs/src/main/resources/css/coredoc.css b/opendj3/opendj-docs/src/main/resources/css/coredoc.css
index 68e6b2b..9403d3c 100644
--- a/opendj3/opendj-docs/src/main/resources/css/coredoc.css
+++ b/opendj3/opendj-docs/src/main/resources/css/coredoc.css
@@ -33,17 +33,19 @@
*/
body
{
- font-family: dejavu, helvetica, verdana, arial, sans-serif;
+ font-family: DejaVu, Verdana, Helvetica, Arial, sans-serif;
/* TODO: is this the right way to restrict width? */
max-width: 800px;
margin-left: auto;
margin-right: auto;
+ color: #333;
}
/* START advice from http://diveintoaccessibility.org/day_26_using_relative_font_sizes.html */
p {
font-size: 12px;
+ line-height: 1.3em;
}
/*/*/a{}
@@ -63,33 +65,67 @@
a
{
text-decoration: none; /* Do not underline links. */
+ font-size: 12px;
+}
+
+a:link {
+ color:#47a;
+}
+
+a:visited {
+ color:#68a;
+}
+
+a:active, a:hover {
+ color:#990000;
+}
+
+code,.command>strong,div.literallayout,.filename
+{
+ font-family: monospace;
+ font-weight: normal;
+}
+
+code,.command,.copyright,div.index,div.literallayout>p,.filename,h3.author,.term,.step
+{
+ font-size: 12px;
+ font-weight: normal;
}
h1
{
- color: #f58220; /* ForgeRock orange */
+ color: #626D75; /* ForgeRock gray */
+ font-size: 24px;
}
h2,h3,h4,h5,h6
{
- color: #626d75; /* ForgeRock gray */
+ color: #333;
}
-/*
- * TODO: In a procedure, number li.step elements as
- * Step 1. <content>
- * Step 2. <content>
- * Step 3. <content>
-
-li.step:before
+h2
{
- content: "Step ";
+ font-size: 17px;
}
-*/
-.term
+h3
{
- font-weight: normal;
+ font-size: 15px;
+}
+
+h3.author:before
+{
+ content: "Written by: ";
+}
+
+h4
+{
+ font-size: 14px;
+}
+
+h5
+{
+ font-size: 13px;
}
ul
@@ -102,13 +138,13 @@
*/
div.navfooter,div.navheader,div.nukefooter
{
- background-color: #efefef; /* TODO: better background color. */
+ background-color: #fafafa;
}
/* Do not repeat the title at the top of the page. */
.navheader th
{
- color: #efefef; /* Same color as background. */
+ color: #fafafa; /* Same color as background. */
font-size: 0px; /* Take up as little space as possible. */
}
@@ -125,15 +161,20 @@
{
font-family: monospace;
white-space: pre;
- background-color: #efefef; /* TODO: better background color. */
- border: thin dashed;
- padding: 10px;
+ background-color: #fafafa;
+ border: thin dashed #ccc;
+ padding: 6px;
}
div.abstract,div.important,div.caution,div.note,div.tip,div.warning,div.example,div.toc
{
- background-color: #efefef; /* TODO: better background color. */
- padding: 10px;
+ border: thin dotted #ccc;
+ padding: 6px;
+}
+
+div.chapter,div.preface
+{
+ border-bottom: thin solid #ccc;
}
.important,.caution,.note,.tip,.warning
@@ -143,11 +184,22 @@
.abstract,.example,.toc
{
- margin: 10px;
+ margin: 6px;
}
img
{
max-width: 640px;
height: auto;
+ max-height: 480px;
}
+
+/*
+ * Man pages
+ */
+.refnamediv>h2,.refsect1>h2,.refsynopsisdiv>h2
+{
+ font-size: 13px;
+}
+
+/* TODO: Man page div content should be indented more than the title. */
\ No newline at end of file
diff --git a/opendj3/pom.xml b/opendj3/pom.xml
index 36a8739..6cb7ba2 100644
--- a/opendj3/pom.xml
+++ b/opendj3/pom.xml
@@ -24,9 +24,7 @@
!
! Copyright 2011 ForgeRock AS
!
--->
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+--><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.forgerock</groupId>
@@ -170,6 +168,13 @@
</execution>
</executions>
</plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-site-plugin</artifactId>
+ <configuration>
+ <locales>en,fr</locales>
+ </configuration>
+ </plugin>
</plugins>
</pluginManagement>
</build>
@@ -212,4 +217,11 @@
</dependency>
</dependencies>
</dependencyManagement>
+ <distributionManagement>
+ <site>
+ <id>opendj.forgerock.org</id>
+ <name>OpenDJ Community</name>
+ <url>scp://opendj.forgerock.org/var/www/vhosts/opendj.forgerock.org/httpdocs</url>
+ </site>
+ </distributionManagement>
</project>
diff --git a/opendj3/src/site/apt/format.apt b/opendj3/src/site/apt/format.apt
new file mode 100644
index 0000000..864419f
--- /dev/null
+++ b/opendj3/src/site/apt/format.apt
@@ -0,0 +1,602 @@
+ -----
+ The APT format
+ -----
+ The Maven Team
+ -----
+ -----
+
+The APT format
+~~~~~~~~~~~~~~
+
+ In the following section, boxes containing text in typewriter-like font are
+ examples of APT source.
+
+* Document structure
+~~~~~~~~~~~~~~~~~~~~
+
+ A short APT document is contained in a single text file. A longer document
+ may be contained in a ordered list of text files. For instance, first text
+ file contains section 1, second text file contains section 2, and so on.
+
+ [Note:] Splitting the APT document in several text files on a section
+ boundary is not mandatory. The split may occur anywhere.
+ However doing so is recommended because a text file containing a
+ section is by itself a valid APT document.
+
+ A file contains a sequence of paragraphs and ``displays'' (non paragraphs
+ such as tables) separated by open lines.
+
+ A paragraph is simply a sequence of consecutive text lines.
+
++------------------------------------------------------------------------+
+ First line of first paragraph.
+ Second line of first paragraph.
+ Third line of first paragraph.
+
+ Line 1 of paragraph 2 (separated from first paragraph by an open line).
+ Line 2 of paragraph 2.
++------------------------------------------------------------------------+
+
+ The indentation of the first line of a paragraph is the main method used by
+ an APT processor to recognize the type of the paragraph. For example, a
+ section title must not be indented at all.
+
+ A ``plain'' paragraph must be indented by a certain amount of space. For
+ example, a plain paragraph which is not contained in a list may be indented
+ by two spaces.
+
++-------------------------------------------------+
+My section title (not indented).
+
+ My paragraph first line (indented by 2 spaces).
++-------------------------------------------------+
+
+ Indentation is not rigid. Any amount of space will do. You don't even need
+ to use a consistent indentation all over your document. What really matters
+ for an APT processor is whether the paragraph is not indented at all or,
+ when inside a list, whether a paragraph is more or less indented than the
+ first item of the list (more about this later).
+
++-------------------------------------------------------+
+ First paragraph has its first line indented by four
+spaces. Then the author did even bother to indent the
+other lines of the paragraph.
+
+ Second paragraph contains several lines which are all
+ indented by two spaces. This style is much nicer than
+ the one used for the previous paragraph.
++-------------------------------------------------------+
+
+ Note that tabs are expanded with a tab width set to 8.
+
+* Document elements
+~~~~~~~~~~~~~~~~~~~
+
+** Block level elements
+~~~~~~~~~~~~~~~~~~~~~~~
+
+*** Title
+~~~~~~~~~~
+
+ A title is optional. If used, it must appear as the first block of the
+ document.
+
++----------------------------------------------------------------------------+
+ ------
+ Title
+ ------
+ Author
+ ------
+ Date
++----------------------------------------------------------------------------+
+
+ A title block is indented (centering it is nicer). It begins with a line
+ containing at least 3 dashes (<<<--->>>).
+
+ After the first <<<--->>> line, one or several consecutive lines of text
+ (implicit line break after each line) specify the title of the document.
+
+ This text may immediately be followed by another <<<--->>> line and one or
+ several consecutive lines of text which specifies the author of the
+ document.
+
+ The author sub-block may optionaly be followed by a date sub-block using the
+ same syntax.
+
+ The following example is used for a document with an title and a date but
+ with no declared author.
+
++----------------------------------------------------------------------------+
+ ------
+ Title
+ ------
+ ------
+ Date
+ ------
++----------------------------------------------------------------------------+
+
+ The last line is ignored. It is just there to make the block nicer.
+
+*** Paragraph
+~~~~~~~~~~~~~
+
+ Paragraphs other than the title block may appear before the first section.
+
++----------------------+
+ Paragraph 1, line 1.
+ Paragraph 1, line 2.
+
+ Paragraph 2, line 1.
+ Paragraph 2, line 2.
++----------------------+
+
+ Paragraphs are indented. They have already been described in the {{document
+ structure}} section.
+
+*** Section
+~~~~~~~~~~~
+
+ Sections are created by inserting section titles into the document. Simple
+ documents need not contain sections.
+
++-----------------------------------+
+Section title
+
+* Sub-section title
+
+** Sub-sub-section title
+
+*** Sub-sub-sub-section title
+
+**** Sub-sub-sub-sub-section title
++-----------------------------------+
+
+ Section titles are not indented. A sub-section title begins with one
+ asterisk (<<<*>>>), a sub-sub-section title begins with two asterisks
+ (<<<**>>>), and so forth up to four sub-section levels.
+
+*** List
+~~~~~~~~
+
++---------------------------------------+
+ * List item 1.
+
+ * List item 2.
+
+ Paragraph contained in list item 2.
+
+ * Sub-list item 1.
+
+ * Sub-list item 2.
+
+ * List item 3.
++---------------------------------------+
+
+ List items are indented and begin with a asterisk (<<<*>>>).
+
+ Plain paragraphs more indented than the first list item are nested in that
+ list. Displays such as tables (not indented) are always nested in the
+ current list.
+
+ To nest a list inside a list, indent its first item more than its parent
+ list. To end a list, add a paragraph or list item less indented than the
+ current list.
+
+ Section titles always end a list. Displays cannot end a list but the
+ <<<[]>>> pseudo-element may be used to force the end of a list.
+
++------------------------------------+
+ * List item 3.
+ Force end of list:
+
+ []
+
+--------------------------------------------
+Verbatim text not contained in list item 3
+--------------------------------------------
++------------------------------------+
+
+ In the previous example, without the <<<[]>>>, the verbatim text (not
+ indented as all displays) would have been contained in list item 3.
+
+ A single <<<[]>>> may be used to end several nested lists at the same
+ time. The indentation of <<<[]>>> may be used to specify exactly which
+ lists should be ended. Example:
+
++------------------------------------+
+ * List item 1.
+
+ * List item 2.
+
+ * Sub-list item 1.
+
+ * Sub-list item 2.
+
+ []
+
+-------------------------------------------------------------------
+Verbatim text contained in list item 2, but not in sub-list item 2
+-------------------------------------------------------------------
++------------------------------------+
+
+ There are three kind of lists, the bulleted lists we have already described,
+ the numbered lists and the definition lists.
+
++-----------------------------------------+
+ [[1]] Numbered item 1.
+
+ [[A]] Numbered item A.
+
+ [[B]] Numbered item B.
+
+ [[2]] Numbered item 2.
++-----------------------------------------+
+
+ A numbered list item begins with a label beetween two square brackets. The
+ label of the first item establishes the numbering scheme for the whole list:
+
+ [<<<[[1\]\]>>>] Decimal numbering: 1, 2, 3, 4, etc.
+
+ [<<<[[a\]\]>>>] Lower-alpha numbering: a, b, c, d, etc.
+
+ [<<<[[A\]\]>>>] Upper-alpha numbering: A, B, C, D, etc.
+
+ [<<<[[i\]\]>>>] Lower-roman numbering: i, ii, iii, iv, etc.
+
+ [<<<[[I\]\]>>>] Upper-roman numbering: I, II, III, IV, etc.
+
+ The labels of the items other than the first one are ignored. It is
+ recommended to take the time to type the correct label for each item in
+ order to keep the APT source document readable.
+
++-------------------------------------------+
+ [Defined term 1] of definition list 2.
+
+ [Defined term 2] of definition list 2.
++-------------------------------------------+
+
+ A definition list item begins with a defined term: text between square
+ brackets.
+
+*** Verbatim text
+~~~~~~~~~~~~~~~~~
+
++----------------------------------------+
+----------------------------------------
+Verbatim
+ text,
+ preformatted,
+ escaped.
+----------------------------------------
++----------------------------------------+
+
+ A verbatim block is not indented. It begins with a non indented line
+ containing at least 3 dashes (<<<--->>>). It ends with a similar line.
+
+ <<<+-->>> instead of <<<--->>> draws a box around verbatim text.
+
+ Like in HTML, verbatim text is preformatted. Unlike HTML, verbatim text is
+ escaped: inside a verbatim display, markup is not interpreted by the APT
+ processor.
+
+*** Figure
+~~~~~~~~~~
+
++---------------------------+
+[Figure name] Figure caption
++---------------------------+
+
+ A figure block is not indented. It begins with the figure name between
+ square brackets. The figure name is optionally followed by some text: the
+ figure caption.
+
+ The figure name is the pathname of the file containing the figure but
+ without an extension. Example: if your figure is contained in
+ <<</home/joe/docs/mylogo.jpeg>>>, the figure name is
+ <<</home/joe/docs/mylogo>>>.
+
+ If the figure name comes from a relative pathname (recommended practice)
+ rather than from an absolute pathname, this relative pathname is taken to be
+ relative to the directory of the current APT document (a la HTML)
+ rather than relative to the current working directory.
+
+ Why not leave the file extension in the figure name? This is better
+ explained by an example. You need to convert an APT document to PostScript
+ and your figure name is <<</home/joe/docs/mylogo>>>. A APT processor will
+ first try to load <<</home/joe/docs/mylogo.eps>>>. When the desired format
+ is not found, a APT processor tries to convert one of the existing
+ formats. In our example, the APT processor tries to convert
+ <<</home/joe/docs/mylogo.jpeg>>> to encapsulated PostScript.
+
+*** Table
+~~~~~~~~~
+
+ A table block is not indented. It begins with a non indented line containing
+ an asterisk and at least 2 dashes (<<<*-->>>). It ends with a
+ similar line.
+
+ The first line is not only used to recognize a table but also to specify
+ column justification. In the following example,
+
+ * the second asterisk (<<<*>>>) is used to specify that column 1 is
+ centered,
+
+ * the plus sign (<<<+>>>) specifies that column 2 is left aligned,
+
+ * the colon (<<<:>>>) specifies that column 3 is right aligned.
+
+ []
+
++---------------------------------------------+
+*----------*--------------+----------------:
+| Centered | Left-aligned | Right-aligned |
+| cell 1,1 | cell 1,2 | cell 1,3 |
+*----------*--------------+----------------:
+| cell 2,1 | cell 2,2 | cell 2,3 |
+*----------*--------------+----------------:
+Table caption
++---------------------------------------------+
+
+ Rows are separated by a non indented line beginning with <<<*-->>>.
+
+ An optional table caption (non indented text) may immediately follow the
+ table.
+
+ Rows may contain single line or multiple line cells. Each line of cell text
+ is separated from the adjacent cell by the pipe character (<<<|>>>).
+ (<<<|>>> may be used in the cell text if quoted: <<<\\|>>>.)
+
+ The last <<<|>>> is only used to make the table nicer. The first <<<|>>> is
+ not only used to make the table nicer, but also to specify that a grid is to
+ be drawn around table cells.
+
+ The following example shows a simple table with no grid and no caption.
+
++---------------+
+*-----*------*
+ cell | cell
+*-----*------*
+ cell | cell
+*-----*------*
++---------------+
+
+*** Horizontal rule
+~~~~~~~~~~~~~~~~~~~
+
++---------------------+
+=====================
++---------------------+
+
+ A non indented line containing at least 3 equal signs (<<<===>>>).
+
+*** Page break
+~~~~~~~~~~~~~~
+
++---+
+^L
++---+
+
+ A non indented line containing a single form feed character (Control-L).
+
+** Text level elements
+~~~~~~~~~~~~~~~~~~~~~~
+
+*** Font
+~~~~~~~~
+
++-----------------------------------------------------+
+ <Italic> font. <<Bold>> font. <<<Monospaced>>> font.
++-----------------------------------------------------+
+
+ Text between \< and > must be rendered in italic. Text between \<\< and >>
+ must be rendered in bold. Text between \<\<\< and >>> must be rendered using
+ a monospaced, typewriter-like font.
+
+ Font elements may appear anywhere except inside other font elements.
+
+ It is not recommended to use font elements inside titles, section titles,
+ links and defined terms because a APT processor automatically applies
+ appropriate font styles to these elements.
+
+*** Anchor and link
+~~~~~~~~~~~~~~~~~~~
+
++-----------------------------------------------------------------+
+ {Anchor}. Link to {{anchor}}. Link to {{http://www.pixware.fr}}.
+ Link to {{{anchor}showing alternate text}}.
+ Link to {{{http://www.pixware.fr}Pixware home page}}.
++-----------------------------------------------------------------+
+
+ Text between curly braces (<<<\{}>>>) specifies an anchor. Text between
+ double curly braces (<<<\{\{}}>>>) specifies a link.
+
+ It is an error to create a link element that does not refer to an anchor of
+ the same name. The name of an anchor/link is its text with all non
+ alphanumeric characters stripped.
+
+ This rule does not apply to links to <external> anchors. Text beginning
+ with <<<http:/>>>, <<<https:/>>>, <<<ftp:/>>>, <<<file:/>>>, <<<mailto:>>>,
+ <<<../>>>, <<<./>>> (<<<..\\>>> and <<<.\\>>> on Windows) is recognized as
+ an external anchor name.
+
+ When the construct <<\{\{\{>><name><<}>><text><<}}>> is used, the link text
+ <text> may differ from the link name <name>.
+
+ Anchor/link elements may appear anywhere except inside other anchor/link
+ elements.
+
+ Section titles are implicitly defined anchors.
+
+*** Line break
+~~~~~~~~~~~~~~
+
++-------------+
+ Force line\
+ break.
++-------------+
+
+ A backslash character (<<<\\>>>) followed by a newline character.
+
+ Line breaks must not be used inside titles and tables (which are line
+ oriented blocks with implicit line breaks).
+
+*** Non breaking space
+~~~~~~~~~~~~~~~~~~~~~~
+
++----------------------+
+ Non\ breaking\ space.
++----------------------+
+
+ A backslash character (<<<\\>>>) followed by a space character.
+
+*** Special character
+~~~~~~~~~~~~~~~~~~~~~
+
++---------------------------------------------------------------------------+
+ Escaped special characters: \~, \=, \-, \+, \*, \[, \], \<, \>, \{, \}, \\.
++---------------------------------------------------------------------------+
+
+ In certain contexts, these characters have a special meaning and therefore
+ must be escaped if needed as is. They are escaped by adding a backslash in
+ front of them. The backslash may itself be escaped by adding another
+ backslash in front of it.
+
+ Note that an asterisk, for example, needs to be escaped only if its begins a
+ paragraph. (<<<*>>> has no special meaning in the middle of a paragraph.)
+
++--------------------------------------+
+ Copyright symbol: \251, \xA9, \u00a9.
++--------------------------------------+
+
+ Latin-1 characters (whatever is the encoding of the APT document) may be
+ specified by their codes using a backslash followed by one to three octal
+ digits or by using the <<<\x>>><NN> notation, where <NN> are two hexadecimal
+ digits.
+
+ Unicode characters may be specified by their codes using the <<<\u>>><NNNN>
+ notation, where <NNNN> are four hexadecimal digits.
+
+*** Comment
+~~~~~~~~~~~
+
++---------------+
+~~Commented out.
++---------------+
+
+ Text found after two tildes (<<<\~~>>>) is ignored up to the end of line.
+
+ A line of <<<~>>> is often used to ``underline'' section titles in order to
+ make them stand out of other paragraphs.
+
+
+* The APT format at a glance
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+------------------------------------------------------------------------------
+ ------
+ Title
+ ------
+ Author
+ ------
+ Date
+
+ Paragraph 1, line 1.
+ Paragraph 1, line 2.
+
+ Paragraph 2, line 1.
+ Paragraph 2, line 2.
+
+Section title
+
+* Sub-section title
+
+** Sub-sub-section title
+
+*** Sub-sub-sub-section title
+
+**** Sub-sub-sub-sub-section title
+
+ * List item 1.
+
+ * List item 2.
+
+ Paragraph contained in list item 2.
+
+ * Sub-list item 1.
+
+ * Sub-list item 2.
+
+ * List item 3.
+ Force end of list:
+
+ []
+
++------------------------------------------+
+Verbatim text not contained in list item 3
++------------------------------------------+
+
+ [[1]] Numbered item 1.
+
+ [[A]] Numbered item A.
+
+ [[B]] Numbered item B.
+
+ [[2]] Numbered item 2.
+
+ List numbering schemes: [[1]], [[a]], [[A]], [[i]], [[I]].
+
+ [Defined term 1] of definition list.
+
+ [Defined term 2] of definition list.
+
++-------------------------------+
+Verbatim text
+ in a box
++-------------------------------+
+
+ --- instead of +-- suppresses the box around verbatim text.
+
+[Figure name] Figure caption
+
+*----------*--------------+----------------:
+| Centered | Left-aligned | Right-aligned |
+| cell 1,1 | cell 1,2 | cell 1,3 |
+*----------*--------------+----------------:
+| cell 2,1 | cell 2,2 | cell 2,3 |
+*----------*--------------+----------------:
+Table caption
+
+ No grid, no caption:
+
+*-----*------*
+ cell | cell
+*-----*------*
+ cell | cell
+*-----*------*
+
+ Horizontal line:
+
+=======================================================================
+
+^L
+ New page.
+
+ <Italic> font. <<Bold>> font. <<<Monospaced>>> font.
+
+ {Anchor}. Link to {{anchor}}. Link to {{http://www.pixware.fr}}.
+ Link to {{{anchor}showing alternate text}}.
+ Link to {{{http://www.pixware.fr}Pixware home page}}.
+
+ Force line\
+ break.
+
+ Non\ breaking\ space.
+
+ Escaped special characters: \~, \=, \-, \+, \*, \[, \], \<, \>, \{, \}, \\.
+
+ Copyright symbol: \251, \xA9, \u00a9.
+
+~~Commented out.
+
+------------------------------------------------------------------------------
+
diff --git a/opendj3/src/site/fml/faq.fml b/opendj3/src/site/fml/faq.fml
new file mode 100644
index 0000000..8d1c52b
--- /dev/null
+++ b/opendj3/src/site/fml/faq.fml
@@ -0,0 +1,147 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ ! CCPL HEADER START
+ !
+ ! This work is licensed under the Creative Commons
+ ! Attribution-NonCommercial-NoDerivs 3.0 Unported License.
+ ! To view a copy of this license, visit
+ ! http://creativecommons.org/licenses/by-nc-nd/3.0/
+ ! or send a letter to Creative Commons, 444 Castro Street,
+ ! Suite 900, Mountain View, California, 94041, USA.
+ !
+ ! You can also obtain a copy of the license at
+ ! src/main/resources/legal-notices/CC-BY-NC-ND.txt.
+ ! See the License for the specific language governing permissions
+ ! and limitations under the License.
+ !
+ ! If applicable, add the following below this CCPL HEADER, with the fields
+ ! enclosed by brackets "[]" replaced with your own identifying information:
+ ! Portions Copyright [yyyy] [name of copyright owner]
+ !
+ ! CCPL HEADER END
+ !
+ ! Copyright 2011 ForgeRock AS
+ !
+-->
+<faqs
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns="http://maven.apache.org/FML/1.0"
+ xsi:schemaLocation="http://maven.apache.org/FML/1.0 http://maven.apache.org/xsd/fml-1.0.xsd"
+ id="OpenDJ FAQ">
+ <part id="General">
+ <faq id="what">
+ <question>What is OpenDJ?</question>
+ <answer>
+ <p>
+ OpenDJ comprises of an open source directory server, client tools, and
+ an LDAP SDK. All modules are 100% Java based and require Java 1.6.
+ </p>
+ <p>
+ OpenDJ is a downstream build of the OpenDS project, with a different
+ name to avoid trademark issues.
+ </p>
+ </answer>
+ </faq>
+ <faq id="why">
+ <question>Why would I want to use OpenDJ? What is it good for?</question>
+ <answer>
+ <p>
+ OpenDJ is a new LDAPv3 compliant directory service, developed for the
+ Java platform, providing a high performance, highly available and secure
+ store for the identities managed by your enterprise. Its easy
+ installation takes OpenDJ the simplest and fastest directory server
+ to deploy and manage.
+ </p>
+ </answer>
+ </faq>
+ <faq id="prerequisites">
+ <question>What are the prerequisites for installing and using OpenDJ?
+ What hardware and software do I need?</question>
+ <answer>
+ <p>
+ At minimum, you need Java 6. If you have Java WebStart configured, you
+ can install OpenDJ server starting with a single click in your web
+ browser. For hardware, you can do an evaluation install on a netbook
+ by default using 256 MB free RAM and less than 100 MB free disk space.
+ How much hardware you need for deployment depends on your requirements.
+ </p>
+ </answer>
+ </faq>
+ <faq id="free">
+ <question>Is OpenDJ free?</question>
+ <answer>
+ <p>
+ You can freely download, evaluate, deploy, even build your own version
+ of OpenDJ software. The license is <a
+ href="http://www.opensource.org/licenses/cddl1">CDDL</a>.
+ </p>
+ </answer>
+ </faq>
+ <faq id="which">
+ <question>Which version of OpenDJ should I use?</question>
+ <answer>
+ <p>
+ Download the latest stable version from the
+ <a href="http://www.forgerock.com/downloads-opendj.html">download
+ page</a>. You can also get the latest nightly build there. If you want
+ to roll your own, check out the <a
+ href="https://wikis.forgerock.org/confluence/display/OPENDJ/Guide+to+OpenDJ+Subversion"
+ >Guide to OpenDJ Subversion</a>.
+ </p>
+ </answer>
+ </faq>
+ <faq id="more">
+ <question>How can I find out more about OpenDJ?</question>
+ <answer>
+ <p>
+ Sign up for the <a
+ href="https://lists.forgerock.org/mailman/listinfo/opendj">OpenDJ
+ mailing list</a>. <a
+ href="https://idp.forgerock.org/openam/UI/Login?service=register">Join
+ the project</a>.
+ Visit the <a href="https://wikis.forgerock.org/confluence/display/OPENDJ/"
+ >OpenDJ Wiki documentation</a>. Chat on irc.freenode.net #opendj.
+ </p>
+ </answer>
+ </faq>
+ <faq id="roadmap">
+ <question>What's the OpenDJ roadmap? Is OpenDJ actively developed?</question>
+ <answer>
+ <p>
+ OpenDJ is actively developed, see <a
+ href="https://bugster.forgerock.org/jira/browse/OPENDJ">the bug database
+ activity</a>. Also see the <a
+ href="https://wikis.forgerock.org/confluence/display/OPENDJ/OpenDJ+Roadmap"
+ >OpenDJ Roadmap</a>.
+ </p>
+ </answer>
+ </faq>
+ <faq id="develop">
+ <question>I want to contribute a patch (a feature, a test, a plug-in)
+ to OpenDJ. How do I get involved?</question>
+ <answer>
+ <p>
+ Come discuss your work on the <a
+ href="https://lists.forgerock.org/mailman/listinfo/opendj-dev">dev mailing
+ list</a>. <a
+ href="https://idp.forgerock.org/openam/UI/Login?service=register">Join
+ the project</a>, too.
+ </p>
+ </answer>
+ </faq>
+ <faq id="test">
+ <question>I want to help test OpenDJ. How do I get started?</question>
+ <answer>
+ <p>
+ Start with the <a
+ href="https://wikis.forgerock.org/confluence/display/OPENDJ/OpenDJ+QA+Documentation"
+ >QA documentation</a>. <a
+ href="https://idp.forgerock.org/openam/UI/Login?service=register">Join
+ the project</a>. Come discuss your work on the <a
+ href="https://lists.forgerock.org/mailman/listinfo/opendj-dev">dev mailing
+ list</a>.
+ </p>
+ </answer>
+ </faq>
+ </part>
+</faqs>
diff --git a/opendj3/src/site/fr/apt/format.apt b/opendj3/src/site/fr/apt/format.apt
new file mode 100644
index 0000000..f8e67c2
--- /dev/null
+++ b/opendj3/src/site/fr/apt/format.apt
@@ -0,0 +1,602 @@
+ -----
+ Le format APT
+ -----
+ L'équipe Maven
+ -----
+ -----
+
+Le format APT
+~~~~~~~~~~~~~
+
+ Dans la section suivante, les boîtes contenant du texte dans la police
+ de type machine à écrire sont des exemples de source APT.
+
+* Structure du document
+~~~~~~~~~~~~~~~~~~~~~~~
+
+ A short APT document is contained in a single text file. A longer document
+ may be contained in a ordered list of text files. For instance, first text
+ file contains section 1, second text file contains section 2, and so on.
+
+ [Note:] Splitting the APT document in several text files on a section
+ boundary is not mandatory. The split may occur anywhere.
+ However doing so is recommended because a text file containing a
+ section is by itself a valid APT document.
+
+ A file contains a sequence of paragraphs and ``displays'' (non paragraphs
+ such as tables) separated by open lines.
+
+ A paragraph is simply a sequence of consecutive text lines.
+
++------------------------------------------------------------------------+
+ First line of first paragraph.
+ Second line of first paragraph.
+ Third line of first paragraph.
+
+ Line 1 of paragraph 2 (separated from first paragraph by an open line).
+ Line 2 of paragraph 2.
++------------------------------------------------------------------------+
+
+ The indentation of the first line of a paragraph is the main method used by
+ an APT processor to recognize the type of the paragraph. For example, a
+ section title must not be indented at all.
+
+ A ``plain'' paragraph must be indented by a certain amount of space. For
+ example, a plain paragraph which is not contained in a list may be indented
+ by two spaces.
+
++-------------------------------------------------+
+My section title (not indented).
+
+ My paragraph first line (indented by 2 spaces).
++-------------------------------------------------+
+
+ Indentation is not rigid. Any amount of space will do. You don't even need
+ to use a consistent indentation all over your document. What really matters
+ for an APT processor is whether the paragraph is not indented at all or,
+ when inside a list, whether a paragraph is more or less indented than the
+ first item of the list (more about this later).
+
++-------------------------------------------------------+
+ First paragraph has its first line indented by four
+spaces. Then the author did even bother to indent the
+other lines of the paragraph.
+
+ Second paragraph contains several lines which are all
+ indented by two spaces. This style is much nicer than
+ the one used for the previous paragraph.
++-------------------------------------------------------+
+
+ Note that tabs are expanded with a tab width set to 8.
+
+* Document elements
+~~~~~~~~~~~~~~~~~~~
+
+** Block level elements
+~~~~~~~~~~~~~~~~~~~~~~~
+
+*** Title
+~~~~~~~~~~
+
+ A title is optional. If used, it must appear as the first block of the
+ document.
+
++----------------------------------------------------------------------------+
+ ------
+ Title
+ ------
+ Author
+ ------
+ Date
++----------------------------------------------------------------------------+
+
+ A title block is indented (centering it is nicer). It begins with a line
+ containing at least 3 dashes (<<<--->>>).
+
+ After the first <<<--->>> line, one or several consecutive lines of text
+ (implicit line break after each line) specify the title of the document.
+
+ This text may immediately be followed by another <<<--->>> line and one or
+ several consecutive lines of text which specifies the author of the
+ document.
+
+ The author sub-block may optionaly be followed by a date sub-block using the
+ same syntax.
+
+ The following example is used for a document with an title and a date but
+ with no declared author.
+
++----------------------------------------------------------------------------+
+ ------
+ Title
+ ------
+ ------
+ Date
+ ------
++----------------------------------------------------------------------------+
+
+ The last line is ignored. It is just there to make the block nicer.
+
+*** Paragraph
+~~~~~~~~~~~~~
+
+ Paragraphs other than the title block may appear before the first section.
+
++----------------------+
+ Paragraph 1, line 1.
+ Paragraph 1, line 2.
+
+ Paragraph 2, line 1.
+ Paragraph 2, line 2.
++----------------------+
+
+ Paragraphs are indented. They have already been described in the {{document
+ structure}} section.
+
+*** Section
+~~~~~~~~~~~
+
+ Sections are created by inserting section titles into the document. Simple
+ documents need not contain sections.
+
++-----------------------------------+
+Section title
+
+* Sub-section title
+
+** Sub-sub-section title
+
+*** Sub-sub-sub-section title
+
+**** Sub-sub-sub-sub-section title
++-----------------------------------+
+
+ Section titles are not indented. A sub-section title begins with one
+ asterisk (<<<*>>>), a sub-sub-section title begins with two asterisks
+ (<<<**>>>), and so forth up to four sub-section levels.
+
+*** List
+~~~~~~~~
+
++---------------------------------------+
+ * List item 1.
+
+ * List item 2.
+
+ Paragraph contained in list item 2.
+
+ * Sub-list item 1.
+
+ * Sub-list item 2.
+
+ * List item 3.
++---------------------------------------+
+
+ List items are indented and begin with a asterisk (<<<*>>>).
+
+ Plain paragraphs more indented than the first list item are nested in that
+ list. Displays such as tables (not indented) are always nested in the
+ current list.
+
+ To nest a list inside a list, indent its first item more than its parent
+ list. To end a list, add a paragraph or list item less indented than the
+ current list.
+
+ Section titles always end a list. Displays cannot end a list but the
+ <<<[]>>> pseudo-element may be used to force the end of a list.
+
++------------------------------------+
+ * List item 3.
+ Force end of list:
+
+ []
+
+--------------------------------------------
+Verbatim text not contained in list item 3
+--------------------------------------------
++------------------------------------+
+
+ In the previous example, without the <<<[]>>>, the verbatim text (not
+ indented as all displays) would have been contained in list item 3.
+
+ A single <<<[]>>> may be used to end several nested lists at the same
+ time. The indentation of <<<[]>>> may be used to specify exactly which
+ lists should be ended. Example:
+
++------------------------------------+
+ * List item 1.
+
+ * List item 2.
+
+ * Sub-list item 1.
+
+ * Sub-list item 2.
+
+ []
+
+-------------------------------------------------------------------
+Verbatim text contained in list item 2, but not in sub-list item 2
+-------------------------------------------------------------------
++------------------------------------+
+
+ There are three kind of lists, the bulleted lists we have already described,
+ the numbered lists and the definition lists.
+
++-----------------------------------------+
+ [[1]] Numbered item 1.
+
+ [[A]] Numbered item A.
+
+ [[B]] Numbered item B.
+
+ [[2]] Numbered item 2.
++-----------------------------------------+
+
+ A numbered list item begins with a label beetween two square brackets. The
+ label of the first item establishes the numbering scheme for the whole list:
+
+ [<<<[[1\]\]>>>] Decimal numbering: 1, 2, 3, 4, etc.
+
+ [<<<[[a\]\]>>>] Lower-alpha numbering: a, b, c, d, etc.
+
+ [<<<[[A\]\]>>>] Upper-alpha numbering: A, B, C, D, etc.
+
+ [<<<[[i\]\]>>>] Lower-roman numbering: i, ii, iii, iv, etc.
+
+ [<<<[[I\]\]>>>] Upper-roman numbering: I, II, III, IV, etc.
+
+ The labels of the items other than the first one are ignored. It is
+ recommended to take the time to type the correct label for each item in
+ order to keep the APT source document readable.
+
++-------------------------------------------+
+ [Defined term 1] of definition list 2.
+
+ [Defined term 2] of definition list 2.
++-------------------------------------------+
+
+ A definition list item begins with a defined term: text between square
+ brackets.
+
+*** Verbatim text
+~~~~~~~~~~~~~~~~~
+
++----------------------------------------+
+----------------------------------------
+Verbatim
+ text,
+ preformatted,
+ escaped.
+----------------------------------------
++----------------------------------------+
+
+ A verbatim block is not indented. It begins with a non indented line
+ containing at least 3 dashes (<<<--->>>). It ends with a similar line.
+
+ <<<+-->>> instead of <<<--->>> draws a box around verbatim text.
+
+ Like in HTML, verbatim text is preformatted. Unlike HTML, verbatim text is
+ escaped: inside a verbatim display, markup is not interpreted by the APT
+ processor.
+
+*** Figure
+~~~~~~~~~~
+
++---------------------------+
+[Figure name] Figure caption
++---------------------------+
+
+ A figure block is not indented. It begins with the figure name between
+ square brackets. The figure name is optionally followed by some text: the
+ figure caption.
+
+ The figure name is the pathname of the file containing the figure but
+ without an extension. Example: if your figure is contained in
+ <<</home/joe/docs/mylogo.jpeg>>>, the figure name is
+ <<</home/joe/docs/mylogo>>>.
+
+ If the figure name comes from a relative pathname (recommended practice)
+ rather than from an absolute pathname, this relative pathname is taken to be
+ relative to the directory of the current APT document (a la HTML)
+ rather than relative to the current working directory.
+
+ Why not leave the file extension in the figure name? This is better
+ explained by an example. You need to convert an APT document to PostScript
+ and your figure name is <<</home/joe/docs/mylogo>>>. A APT processor will
+ first try to load <<</home/joe/docs/mylogo.eps>>>. When the desired format
+ is not found, a APT processor tries to convert one of the existing
+ formats. In our example, the APT processor tries to convert
+ <<</home/joe/docs/mylogo.jpeg>>> to encapsulated PostScript.
+
+*** Table
+~~~~~~~~~
+
+ A table block is not indented. It begins with a non indented line containing
+ an asterisk and at least 2 dashes (<<<*-->>>). It ends with a
+ similar line.
+
+ The first line is not only used to recognize a table but also to specify
+ column justification. In the following example,
+
+ * the second asterisk (<<<*>>>) is used to specify that column 1 is
+ centered,
+
+ * the plus sign (<<<+>>>) specifies that column 2 is left aligned,
+
+ * the colon (<<<:>>>) specifies that column 3 is right aligned.
+
+ []
+
++---------------------------------------------+
+*----------*--------------+----------------:
+| Centered | Left-aligned | Right-aligned |
+| cell 1,1 | cell 1,2 | cell 1,3 |
+*----------*--------------+----------------:
+| cell 2,1 | cell 2,2 | cell 2,3 |
+*----------*--------------+----------------:
+Table caption
++---------------------------------------------+
+
+ Rows are separated by a non indented line beginning with <<<*-->>>.
+
+ An optional table caption (non indented text) may immediately follow the
+ table.
+
+ Rows may contain single line or multiple line cells. Each line of cell text
+ is separated from the adjacent cell by the pipe character (<<<|>>>).
+ (<<<|>>> may be used in the cell text if quoted: <<<\\|>>>.)
+
+ The last <<<|>>> is only used to make the table nicer. The first <<<|>>> is
+ not only used to make the table nicer, but also to specify that a grid is to
+ be drawn around table cells.
+
+ The following example shows a simple table with no grid and no caption.
+
++---------------+
+*-----*------*
+ cell | cell
+*-----*------*
+ cell | cell
+*-----*------*
++---------------+
+
+*** Horizontal rule
+~~~~~~~~~~~~~~~~~~~
+
++---------------------+
+=====================
++---------------------+
+
+ A non indented line containing at least 3 equal signs (<<<===>>>).
+
+*** Page break
+~~~~~~~~~~~~~~
+
++---+
+^L
++---+
+
+ A non indented line containing a single form feed character (Control-L).
+
+** Text level elements
+~~~~~~~~~~~~~~~~~~~~~~
+
+*** Font
+~~~~~~~~
+
++-----------------------------------------------------+
+ <Italic> font. <<Bold>> font. <<<Monospaced>>> font.
++-----------------------------------------------------+
+
+ Text between \< and > must be rendered in italic. Text between \<\< and >>
+ must be rendered in bold. Text between \<\<\< and >>> must be rendered using
+ a monospaced, typewriter-like font.
+
+ Font elements may appear anywhere except inside other font elements.
+
+ It is not recommended to use font elements inside titles, section titles,
+ links and defined terms because a APT processor automatically applies
+ appropriate font styles to these elements.
+
+*** Anchor and link
+~~~~~~~~~~~~~~~~~~~
+
++-----------------------------------------------------------------+
+ {Anchor}. Link to {{anchor}}. Link to {{http://www.pixware.fr}}.
+ Link to {{{anchor}showing alternate text}}.
+ Link to {{{http://www.pixware.fr}Pixware home page}}.
++-----------------------------------------------------------------+
+
+ Text between curly braces (<<<\{}>>>) specifies an anchor. Text between
+ double curly braces (<<<\{\{}}>>>) specifies a link.
+
+ It is an error to create a link element that does not refer to an anchor of
+ the same name. The name of an anchor/link is its text with all non
+ alphanumeric characters stripped.
+
+ This rule does not apply to links to <external> anchors. Text beginning
+ with <<<http:/>>>, <<<https:/>>>, <<<ftp:/>>>, <<<file:/>>>, <<<mailto:>>>,
+ <<<../>>>, <<<./>>> (<<<..\\>>> and <<<.\\>>> on Windows) is recognized as
+ an external anchor name.
+
+ When the construct <<\{\{\{>><name><<}>><text><<}}>> is used, the link text
+ <text> may differ from the link name <name>.
+
+ Anchor/link elements may appear anywhere except inside other anchor/link
+ elements.
+
+ Section titles are implicitly defined anchors.
+
+*** Line break
+~~~~~~~~~~~~~~
+
++-------------+
+ Force line\
+ break.
++-------------+
+
+ A backslash character (<<<\\>>>) followed by a newline character.
+
+ Line breaks must not be used inside titles and tables (which are line
+ oriented blocks with implicit line breaks).
+
+*** Non breaking space
+~~~~~~~~~~~~~~~~~~~~~~
+
++----------------------+
+ Non\ breaking\ space.
++----------------------+
+
+ A backslash character (<<<\\>>>) followed by a space character.
+
+*** Special character
+~~~~~~~~~~~~~~~~~~~~~
+
++---------------------------------------------------------------------------+
+ Escaped special characters: \~, \=, \-, \+, \*, \[, \], \<, \>, \{, \}, \\.
++---------------------------------------------------------------------------+
+
+ In certain contexts, these characters have a special meaning and therefore
+ must be escaped if needed as is. They are escaped by adding a backslash in
+ front of them. The backslash may itself be escaped by adding another
+ backslash in front of it.
+
+ Note that an asterisk, for example, needs to be escaped only if its begins a
+ paragraph. (<<<*>>> has no special meaning in the middle of a paragraph.)
+
++--------------------------------------+
+ Copyright symbol: \251, \xA9, \u00a9.
++--------------------------------------+
+
+ Latin-1 characters (whatever is the encoding of the APT document) may be
+ specified by their codes using a backslash followed by one to three octal
+ digits or by using the <<<\x>>><NN> notation, where <NN> are two hexadecimal
+ digits.
+
+ Unicode characters may be specified by their codes using the <<<\u>>><NNNN>
+ notation, where <NNNN> are four hexadecimal digits.
+
+*** Comment
+~~~~~~~~~~~
+
++---------------+
+~~Commented out.
++---------------+
+
+ Text found after two tildes (<<<\~~>>>) is ignored up to the end of line.
+
+ A line of <<<~>>> is often used to ``underline'' section titles in order to
+ make them stand out of other paragraphs.
+
+
+* The APT format at a glance
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+------------------------------------------------------------------------------
+ ------
+ Title
+ ------
+ Author
+ ------
+ Date
+
+ Paragraph 1, line 1.
+ Paragraph 1, line 2.
+
+ Paragraph 2, line 1.
+ Paragraph 2, line 2.
+
+Section title
+
+* Sub-section title
+
+** Sub-sub-section title
+
+*** Sub-sub-sub-section title
+
+**** Sub-sub-sub-sub-section title
+
+ * List item 1.
+
+ * List item 2.
+
+ Paragraph contained in list item 2.
+
+ * Sub-list item 1.
+
+ * Sub-list item 2.
+
+ * List item 3.
+ Force end of list:
+
+ []
+
++------------------------------------------+
+Verbatim text not contained in list item 3
++------------------------------------------+
+
+ [[1]] Numbered item 1.
+
+ [[A]] Numbered item A.
+
+ [[B]] Numbered item B.
+
+ [[2]] Numbered item 2.
+
+ List numbering schemes: [[1]], [[a]], [[A]], [[i]], [[I]].
+
+ [Defined term 1] of definition list.
+
+ [Defined term 2] of definition list.
+
++-------------------------------+
+Verbatim text
+ in a box
++-------------------------------+
+
+ --- instead of +-- suppresses the box around verbatim text.
+
+[Figure name] Figure caption
+
+*----------*--------------+----------------:
+| Centered | Left-aligned | Right-aligned |
+| cell 1,1 | cell 1,2 | cell 1,3 |
+*----------*--------------+----------------:
+| cell 2,1 | cell 2,2 | cell 2,3 |
+*----------*--------------+----------------:
+Table caption
+
+ No grid, no caption:
+
+*-----*------*
+ cell | cell
+*-----*------*
+ cell | cell
+*-----*------*
+
+ Horizontal line:
+
+=======================================================================
+
+^L
+ New page.
+
+ <Italic> font. <<Bold>> font. <<<Monospaced>>> font.
+
+ {Anchor}. Link to {{anchor}}. Link to {{http://www.pixware.fr}}.
+ Link to {{{anchor}showing alternate text}}.
+ Link to {{{http://www.pixware.fr}Pixware home page}}.
+
+ Force line\
+ break.
+
+ Non\ breaking\ space.
+
+ Escaped special characters: \~, \=, \-, \+, \*, \[, \], \<, \>, \{, \}, \\.
+
+ Copyright symbol: \251, \xA9, \u00a9.
+
+~~Commented out.
+
+------------------------------------------------------------------------------
+
diff --git a/opendj3/src/site/fr/apt/index.apt b/opendj3/src/site/fr/apt/index.apt
new file mode 100644
index 0000000..dde1c9f
--- /dev/null
+++ b/opendj3/src/site/fr/apt/index.apt
@@ -0,0 +1,17 @@
+ -----
+ Le Site
+ -----
+ L'équipe Maven
+ -----
+
+Site Maven pour votre projet
+
+ Félicitations! Si vous regardez cette page alors vous avez
+ généré avec succès un modèle de site en utilisant l'archétype
+ de site et vous avez lancé :
+
++-----+
+
+mvn site
+
++-----+
diff --git a/opendj3/src/site/fr/fml/faq.fml b/opendj3/src/site/fr/fml/faq.fml
new file mode 100644
index 0000000..22ab255
--- /dev/null
+++ b/opendj3/src/site/fr/fml/faq.fml
@@ -0,0 +1,27 @@
+<?xml version="1.0"?>
+<faqs xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/FML/1.0"
+ xsi:schemaLocation="http://maven.apache.org/FML/1.0 http://maven.apache.org/xsd/fml-1.0.xsd"
+ id="FAQ Général">
+ <part id="General">
+ <faq id="where">
+ <question>D'où vient Maven ?</question>
+ <answer>
+ <p>
+ Maven was created by a group of software developers who were tired
+ of wasting their time fiddling around with builds and wanted to get
+ down to brass tacks and actually develop software!
+ </p>
+ </answer>
+ </faq>
+ <faq id="why">
+ <question>Pourquoi Maven est-il si populaire ?</question>
+ <answer>
+ <p>
+ Maven saves you so much time in your software development efforts that
+ you will have time to learn a second language, relax ten hours a
+ day, and train for that marathon you've always wanted to run!
+ </p>
+ </answer>
+ </faq>
+ </part>
+</faqs>
diff --git a/opendj3/src/site/fr/xdoc/xdoc.xml b/opendj3/src/site/fr/xdoc/xdoc.xml
new file mode 100644
index 0000000..49e79bb
--- /dev/null
+++ b/opendj3/src/site/fr/xdoc/xdoc.xml
@@ -0,0 +1,17 @@
+<?xml version="1.0"?>
+<document xmlns="http://maven.apache.org/XDOC/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd">
+ <properties>
+ <title>Bienvenue</title>
+ <author email="dev@maven.apache.org">The Maven Team</author>
+ </properties>
+
+ <body>
+ <section name="Bienvenue dans un fichier XDOC!">
+ <p>
+ Ceci est du texte pour le fichier xdoc.
+ </p>
+ </section>
+ </body>
+</document>
+
diff --git a/opendj3/src/site/site.xml b/opendj3/src/site/site.xml
new file mode 100644
index 0000000..f341dd9
--- /dev/null
+++ b/opendj3/src/site/site.xml
@@ -0,0 +1,104 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ ! CCPL HEADER START
+ !
+ ! This work is licensed under the Creative Commons
+ ! Attribution-NonCommercial-NoDerivs 3.0 Unported License.
+ ! To view a copy of this license, visit
+ ! http://creativecommons.org/licenses/by-nc-nd/3.0/
+ ! or send a letter to Creative Commons, 444 Castro Street,
+ ! Suite 900, Mountain View, California, 94041, USA.
+ !
+ ! You can also obtain a copy of the license at
+ ! src/main/resources/legal-notices/CC-BY-NC-ND.txt.
+ ! See the License for the specific language governing permissions
+ ! and limitations under the License.
+ !
+ ! If applicable, add the following below this CCPL HEADER, with the fields
+ ! enclosed by brackets "[]" replaced with your own identifying information:
+ ! Portions Copyright [yyyy] [name of copyright owner]
+ !
+ ! CCPL HEADER END
+ !
+ ! Copyright 2011 ForgeRock AS
+ !
+-->
+<project name="${project.name}"
+ xmlns="http://maven.apache.org/DECORATION/1.0.1"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/DECORATION/1.0.1 http://maven.apache.org/xsd/decoration-1.0.1.xsd">
+
+ <skin>
+ <groupId>org.forgerock.commons</groupId>
+ <artifactId>forgerock-community-skin</artifactId>
+ <version>1.0.0-SNAPSHOT</version>
+ </skin>
+ <publishDate position="right" format="yyyy.MM.dd" />
+ <version position="right" />
+
+ <!-- TODO: Add Google Analytics -->
+
+ <body>
+
+ <breadcrumbs>
+ <item name="Developer Community" href="http://www.forgerock.org" />
+ <item name="OpenDJ" href="http://opendj.forgerock.org" />
+ </breadcrumbs>
+
+ <menu name="OpenDJ">
+ <item name="Welcome" href="index.html" />
+ <item name="News" href="news.html" />
+ <item name="Join" href="https://idp.forgerock.org/openam/UI/Login?service=register" />
+ <item name="Downloads" href="http://www.forgerock.com/downloads-opendj.html" />
+ <item name="FAQ" href="faq.html" />
+ <item name="Mailing List" href="https://lists.forgerock.org/mailman/listinfo/opendj" />
+ <item name="Support" href="http://www.forgerock.com/subscriptions.html" />
+ <item name="Partners" href="http://www.forgerock.com/partners.html" />
+ <item name="Wiki" href="http://wikis.forgerock.org/opendj/" />
+ </menu>
+
+ <menu name="Core Documentation">
+ <item name="Release Notes" href="index.html" collapse="true">
+ <item name="EPUB Format" href="./doc/OpenDJ-Release-Notes.epub"/>
+ <item name="HTML Format" href="./doc/release-notes/OpenDJ-Release-Notes.html"/>
+ <item name="PDF Format" href="./doc/OpenDJ-Release-Notes.pdf" />
+ <item name="RTF Format" href="./doc/OpenDJ-Release-Notes.rtf" />
+ </item>
+ <item name="Installation Guide" href="index.html" collapse="true">
+ <item name="EPUB Format" href="./doc/OpenDJ-Install-Guide.epub"/>
+ <item name="HTML Format" href="./doc/install-guide/OpenDJ-Install-Guide.html" />
+ <item name="PDF Format" href="./doc/OpenDJ-Install-Guide.pdf" />
+ <item name="RTF Format" href="./doc/OpenDJ-Install-Guide.rtf" />
+ </item>
+ <item name="Administration Guide" href="index.html" collapse="true">
+ <item name="EPUB Format" href="./doc/OpenDJ-Admin-Guide.epub" />
+ <item name="HTML Format" href="./doc/admin-guide/OpenDJ-Admin-Guide.html" />
+ <item name="PDF Format" href="./doc/OpenDJ-Admin-Guide.pdf" />
+ <item name="RTF Format" href="./doc/OpenDJ-Admin-Guide.rtf" />
+ </item>
+ <item name="Developer Guide" href="index.html" collapse="true">
+ <item name="EPUB Format" href="./doc/OpenDJ-Dev-Guide.epub" />
+ <item name="HTML Format" href="./doc/dev-guide/OpenDJ-Dev-Guide.html" />
+ <item name="PDF Format" href="./doc/OpenDJ-Dev-Guide.pdf" />
+ <item name="RTF Format" href="./doc/OpenDJ-Dev-Guide.rtf" />
+ </item>
+ <item name="Config Reference" href="index.html" alt="TODO" />
+ <item name="Plugin Javadoc" href="index.html" alt="TODO" />
+ <item name="SDK Javadoc" href="index.html" alt="TODO" />
+ </menu>
+
+ <!-- TODO: Add QA pages -->
+
+ <menu ref="reports" />
+
+ </body>
+
+ <custom>
+ <openproject>
+ <href>http://opendj.org/</href>
+ <src>./images/opendj-tagline-179x65.png</src>
+ <alt>OpenDJ</alt>
+ </openproject>
+ </custom>
+
+</project>
diff --git a/opendj3/src/site/site_fr.xml b/opendj3/src/site/site_fr.xml
new file mode 100644
index 0000000..d1fd757
--- /dev/null
+++ b/opendj3/src/site/site_fr.xml
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<project name="Maven" xmlns="http://maven.apache.org/DECORATION/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/DECORATION/1.0.0 http://maven.apache.org/xsd/decoration-1.0.0.xsd">
+ <bannerLeft>
+ <name>Maven</name>
+ <src>http://maven.apache.org/images/apache-maven-project.png</src>
+ <href>http://maven.apache.org/</href>
+ </bannerLeft>
+ <bannerRight>
+ <src>http://maven.apache.org/images/maven-small.gif</src>
+ </bannerRight>
+
+ <body>
+ <links>
+ <item name="Apache" href="http://www.apache.org/" />
+ <item name="Maven 1.0" href="http://maven.apache.org/"/>
+ <item name="Maven 2" href="http://maven.apache.org/maven2/"/>
+ </links>
+
+ <menu name="Maven 2.0">
+ <item name="Format APT" href="format.html"/>
+ <item name="FAQ" href="faq.html"/>
+ <item name="Exemple Xdoc" href="xdoc.html"/>
+ </menu>
+ </body>
+</project>
diff --git a/opendj3/src/site/xdoc/index.xml b/opendj3/src/site/xdoc/index.xml
new file mode 100644
index 0000000..79d88ad
--- /dev/null
+++ b/opendj3/src/site/xdoc/index.xml
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ ! CCPL HEADER START
+ !
+ ! This work is licensed under the Creative Commons
+ ! Attribution-NonCommercial-NoDerivs 3.0 Unported License.
+ ! To view a copy of this license, visit
+ ! http://creativecommons.org/licenses/by-nc-nd/3.0/
+ ! or send a letter to Creative Commons, 444 Castro Street,
+ ! Suite 900, Mountain View, California, 94041, USA.
+ !
+ ! You can also obtain a copy of the license at
+ ! src/main/resources/legal-notices/CC-BY-NC-ND.txt.
+ ! See the License for the specific language governing permissions
+ ! and limitations under the License.
+ !
+ ! If applicable, add the following below this CCPL HEADER, with the fields
+ ! enclosed by brackets "[]" replaced with your own identifying information:
+ ! Portions Copyright [yyyy] [name of copyright owner]
+ !
+ ! CCPL HEADER END
+ !
+ ! Copyright 2011 ForgeRock AS
+ !
+-->
+<document
+ xmlns="http://maven.apache.org/XDOC/2.0"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd">
+ <properties>
+ <title>About OpenDJ</title>
+ <author email="opendj-dev@forgerock.org">ForgeRock AS</author>
+ </properties>
+ <body>
+ <section name="About OpenDJ">
+ <p>The OpenDJ community actively develops open source directory services,
+ including a high performance, highly available, secure directory server,
+ built-in data replication, client tools, and an LDAP SDK. OpenDJ offers
+ extensive LDAPv3 support. OpenDJ DSML gateway enables applications
+ accessing directory data through DSMLv2. All modules are 100% Java based
+ and require Java 1.6.</p>
+ <p>Coming soon on the <a
+ href="https://wikis.forgerock.org/confluence/display/OPENDJ/OpenDJ+Roadmap"
+ >OpenDJ Roadmap</a>, you see that the community plans to add RESTful web
+ services access to the directory, and to develop directory proxy services
+ with virtual directory capabilities such as data mapping and connectors
+ for non-directory data sources.</p>
+ </section>
+ <section name="Welcome Users">
+ <p>The OpenDJ community shares an interest in improving and extending
+ OpenDJ software, and in adapting OpenDJ to best fit our needs.</p>
+ <p>You are welcome to join us. Here are some ways to get started.</p>
+ <ul>
+ <li>Download and install a build from the <a
+ href="http://www.forgerock.com/downloads-opendj.html">download page</a>.</li>
+ <li>Join the <a
+ href="https://lists.forgerock.org/mailman/listinfo/opendj">OpenDJ
+ mailing list</a> to ask questions, make suggestions, and tell us what
+ you think of OpenDJ.</li>
+ <li><a
+ href="https://idp.forgerock.org/openam/UI/Login?service=register">Register
+ to join the community</a>.</li>
+ <li>Read and edit <a
+ href="https://wikis.forgerock.org/confluence/display/OPENDJ/">OpenDJ Wiki
+ documentation</a>.</li>
+ <li>Chat on irc.freenode.net #opendj.</li>
+ </ul>
+ <p>Looking forward to hearing from you.</p>
+ </section>
+ <section name="Welcome Developers">
+ <p>If you are a Java developer interested in OpenDJ, there are plenty of
+ ways you can get actively involved in the community in addition to joining
+ as an OpenDJ user.</p>
+ <ul>
+ <li>Get the source. See instructions in the <a
+ href="https://wikis.forgerock.org/confluence/display/OPENDJ/Guide+to+OpenDJ+Subversion"
+ >Guide to OpenDJ Subversion</a>.</li>
+ <li>Make sure you <a
+ href="https://idp.forgerock.org/openam/UI/Login?service=register">register
+ to join the community</a>, thus also registering to <a
+ href="https://bugster.forgerock.org/jira/browse/OPENDJ">report issues, and
+ describe requests for enhancements</a>, as well as to edit <a
+ href="https://wikis.forgerock.org/confluence/display/OPENDJ/">OpenDJ Wiki
+ documentation</a>.</li>
+ <li>Participate and discuss your work on the <a
+ href="https://lists.forgerock.org/mailman/listinfo/opendj-dev">OpenDJ
+ developer mailing list</a> in addition to the <a
+ href="https://lists.forgerock.org/mailman/listinfo/opendj">OpenDJ
+ mailing list</a>.</li>
+ </ul>
+ </section>
+ <section name="Welcome Partners">
+ <p>Want to partner with other OpenDJ community members to bring solutions
+ based on OpenDJ to your customers?</p>
+ <ul>
+ <li>Come show off your expertise on the <a
+ href="https://lists.forgerock.org/mailman/listinfo/opendj">mailing list</a>
+ and in the chat room at irc.freenode.net #opendj.</li>
+ <li>Post your success stories and white papers on the <a
+ href="https://wikis.forgerock.org/confluence/display/OPENDJ/">OpenDJ
+ Wiki</a>.</li>
+ </ul>
+ </section>
+ </body>
+</document>
+
diff --git a/opendj3/src/site/xdoc/news.xml b/opendj3/src/site/xdoc/news.xml
new file mode 100644
index 0000000..3eacba3
--- /dev/null
+++ b/opendj3/src/site/xdoc/news.xml
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ ! CCPL HEADER START
+ !
+ ! This work is licensed under the Creative Commons
+ ! Attribution-NonCommercial-NoDerivs 3.0 Unported License.
+ ! To view a copy of this license, visit
+ ! http://creativecommons.org/licenses/by-nc-nd/3.0/
+ ! or send a letter to Creative Commons, 444 Castro Street,
+ ! Suite 900, Mountain View, California, 94041, USA.
+ !
+ ! You can also obtain a copy of the license at
+ ! src/main/resources/legal-notices/CC-BY-NC-ND.txt.
+ ! See the License for the specific language governing permissions
+ ! and limitations under the License.
+ !
+ ! If applicable, add the following below this CCPL HEADER, with the fields
+ ! enclosed by brackets "[]" replaced with your own identifying information:
+ ! Portions Copyright [yyyy] [name of copyright owner]
+ !
+ ! CCPL HEADER END
+ !
+ ! Copyright 2011 ForgeRock AS
+ !
+-->
+<document
+ xmlns="http://maven.apache.org/XDOC/2.0"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd">
+ <properties>
+ <title>OpenDJ News</title>
+ <author email="opendj-dev@forgerock.org">ForgeRock AS</author>
+ </properties>
+ <body>
+ <section name="New Site">
+ <p>Welcome to the new OpenDJ community site!</p>
+ </section>
+ <section name="New Releases">
+ <p>April 24, 2011. OpenDJ 2.4.2 is out! Come get 2.4.2 from the <a
+ href="http://www.forgerock.com/downloads-opendj.html">download page</a>.</p>
+
+ <p>March 2, 2011. OpenDJ 2.4.1 now available! Get it from the <a
+ href="http://www.forgerock.com/downloads-opendj.html">download page</a>.</p>
+ </section>
+ </body>
+</document>
+
--
Gitblit v1.10.0