Return-Path: 
 <dev-return-15485-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org>
Delivered-To: apmail-forrest-dev-archive@www.apache.org
Received: (qmail 98527 invoked from network); 31 Mar 2005 22:05:27 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 31 Mar 2005 22:05:27 -0000
Received: (qmail 10766 invoked by uid 500); 31 Mar 2005 22:05:27 -0000
Delivered-To: apmail-forrest-dev-archive@forrest.apache.org
Received: (qmail 10571 invoked by uid 500); 31 Mar 2005 22:05:26 -0000
Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@forrest.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@forrest.apache.org>
List-Post: <mailto:dev@forrest.apache.org>
Reply-To: dev@forrest.apache.org
Delivered-To: mailing list dev@forrest.apache.org
Received: (qmail 10557 invoked by uid 99); 31 Mar 2005 22:05:26 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Received: from web81603.mail.yahoo.com (HELO web81603.mail.yahoo.com)
 (206.190.37.120)
  by apache.org (qpsmtpd/0.28) with SMTP; Thu, 31 Mar 2005 14:05:25 -0800
Message-ID: <20050331220521.93616.qmail@web81603.mail.yahoo.com>
Received: from [63.202.83.131] by web81603.mail.yahoo.com via HTTP;
 Thu, 31 Mar 2005 14:05:21 PST
Date: Thu, 31 Mar 2005 14:05:21 -0800 (PST)
From: Jeff Levitt <derby@mylevita.com>
Subject: Re: DITA plugin (Derby history)
To: dev@forrest.apache.org
In-Reply-To: 6667
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


--- Ross Gardler <rgardler@apache.org> wrote:
<snip>
> However, in this case since we know all the docs
> that we *don't* want to 
> process are DITA files I *think* we will simply be
> able to turn off the 
> DITA plugin and catch the exceptions the Forrest
> throws because it can't 
> find the file it needs.
></snip>

One other item to note:

The dita files use a ditamap for proper organization. 
The .ditamap file calls each .dita file in the proper
order, so you actually call the ditamap file for
processing in the toolkit, and the toolkit processes
each dita file that it encounters in the ditamap. So I
think the plugin should also do it this way...