Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <20050331184900.77298.qmail@web81608.mail.yahoo.com>
Date: Thu, 31 Mar 2005 10:49:00 -0800 (PST)
From: Jeff Levitt <derby@mylevita.com>
Subject: Re: Problems building DITA docs
To: Derby Development <derby-dev@db.apache.org>
In-Reply-To: 6667
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


--- Jeff Levitt <derby@mylevita.com> wrote:

> So with this new development, I now suspect that
> something in our ant file or the way that it calls
> the
> jar files or the xsl files is different than what
> was
> in the original build file....any guesses?

Fred and Scott,

I'd like you each to try to build the docs using the
original ant file.  If you also get successful builds,
then we can confirm that the ant file we have modified
is the problem.  Here's what to do:

Run ant from the trunk/DITA-OT1.0/ directory instead
of from trunk/.  The original ant build.xml file is in
that directory.  You will get a series of prompts. 
For the first prompt, enter the full location of the
ditamap that fails on your machine.  For Fred, it was
the getting started guide.  For Scott, I think it was
the reference manual.  For me on Windows, it was the
adminguide, so for example I enter:

C:\derby\trunk\src\adminguide\derbyadmin.ditamap

For the next prompt, just use the default out
diretory.  The third prompt asks for an output format.
 Enter PDF.

Enter a "y" for the final prompt.

You will get a bunch of errors and warnings, more than
usual (because Andrew's build file fixed a lot of
those) but you SHOULD get a BUILD SUCCESSFUL message
at the end, which is what we need to see.  Please let
us all know if that is what you get.  I am crossing my
fingers :)

Jeff