Return-Path:
Delivered-To: apmail-forrest-svn-archive@www.apache.org
Received: (qmail 2914 invoked from network); 18 May 2006 17:53:21 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
by minotaur.apache.org with SMTP; 18 May 2006 17:53:21 -0000
Received: (qmail 84272 invoked by uid 500); 18 May 2006 17:53:20 -0000
Delivered-To: apmail-forrest-svn-archive@forrest.apache.org
Received: (qmail 84232 invoked by uid 500); 18 May 2006 17:53:20 -0000
Mailing-List: contact svn-help@forrest.apache.org; run by ezmlm
Precedence: bulk
list-help:
list-unsubscribe:
List-Post:
Reply-To: "Forrest Developers List"
List-Id:
Delivered-To: mailing list svn@forrest.apache.org
Received: (qmail 84220 invoked by uid 99); 18 May 2006 17:53:20 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 May 2006 10:53:20 -0700
X-ASF-Spam-Status: No, hits=0.6 required=10.0
tests=NO_REAL_NAME
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [140.211.166.113] (HELO eris.apache.org) (140.211.166.113)
by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 May 2006 10:53:19 -0700
Received: by eris.apache.org (Postfix, from userid 65534)
id 76DC21A9835; Thu, 18 May 2006 10:52:59 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r407597 - in /forrest/trunk/site-author/content/xdocs:
contrib.xml flyer.xml guidelines.xml howto-dev.xml index.xml site.xml
Date: Thu, 18 May 2006 17:52:57 -0000
To: svn@forrest.apache.org
From: ferdinand@apache.org
X-Mailer: svnmailer-1.0.8
Message-Id: <20060518175259.76DC21A9835@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N
Author: ferdinand
Date: Thu May 18 10:52:57 2006
New Revision: 407597
URL: http://svn.apache.org/viewvc?rev=407597&view=rev
Log:
Fixing and correcting links after restructuring
Modified:
forrest/trunk/site-author/content/xdocs/contrib.xml
forrest/trunk/site-author/content/xdocs/flyer.xml
forrest/trunk/site-author/content/xdocs/guidelines.xml
forrest/trunk/site-author/content/xdocs/howto-dev.xml
forrest/trunk/site-author/content/xdocs/index.xml
forrest/trunk/site-author/content/xdocs/site.xml
Modified: forrest/trunk/site-author/content/xdocs/contrib.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/contrib.xml?rev=407597&r1=407596&r2=407597&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/contrib.xml (original)
+++ forrest/trunk/site-author/content/xdocs/contrib.xml Thu May 18 10:52:57 2006
@@ -150,7 +150,7 @@
method is appropriate for a certain situation and how to go about it without
confusion. This section explains when to use the developer
mailing list and the
- issue tracker.
+ issue tracker.
Research your topic thoroughly before beginning to discuss a new
development issue. Search and browse through the email archives - your issue
may have been discussed before. Prepare your post clearly and concisely.
Multiple task-specific source XML formats can be used
- (How-To,
- How-To,
+ FAQ,
changelogs and
- todo lists supported natively).
+ todo lists supported natively).
Source formats include: Apache xdocs xml format, plain html
documents, some Wiki formats, a subset of DocBook, ...
Committers add an entry for each significant contribution to the
- top-level changes document (site-author/status.xml)
+ top-level changes document (site-author/status.xml)
and detailed entries to the relevant plugin's changes document. This enables linkage
to the relevant issue and shows the contributor's name. It also shows
the initials of the committer who did the work to add the patch.
Modified: forrest/trunk/site-author/content/xdocs/howto-dev.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/howto-dev.xml?rev=407597&r1=407596&r2=407597&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/howto-dev.xml (original)
+++ forrest/trunk/site-author/content/xdocs/howto-dev.xml Thu May 18 10:52:57 2006
@@ -108,7 +108,7 @@
integrated development environments such as Eclipse or IDEA.
- Ensure to configure your xml editor to take
+ Ensure to configure your xml editor to take
advantage of the local sets of DTDs provided by Forrest. This also explains how
to use xml validators such as 'xmllint'. If your editor of choice doesn't
validate XML, then most XML validation issues can be discovered using
@@ -147,7 +147,7 @@
To get started, see the
- instructions
+ instructions
for obtaining the Apache Forrest sources via SVN.
@@ -330,11 +330,11 @@
The Cocoon sitemap is essential for Forrest developers. See some introductions ....