You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Jean T. Anderson" <jt...@bristowhill.com> on 2006/08/25 05:49:04 UTC
Doc build fails with DERBY-1655 patch (was Re: [jira] Updated: (DERBY-1655)
Document XML functionality for 10.2)
Army wrote:
...
> Just in case Jira is still backlogged, I vote +1 to have the
> derby1655_ref5.diff changes committed.
After applying derby1655_ref5.diff 'ant html' succeeds for me but,
unfortunately, 'ant pdf' and 'ant monohtml' both fail with these initial
warnings:
[xslt]
file:/home/jta/DB-DERBY-SVN/derby/docs/trunk/DITA-OT1.1.2.1/xsl/xslfo/dita2fo-links.xsl:148:57:
Warning! Can not load requested doc: White spaces are required between
publicId and systemId.
[xslt]
file:/home/jta/DB-DERBY-SVN/derby/docs/trunk/DITA-OT1.1.2.1/xsl/xslfo/dita2fo-links.xsl:148:57:
Warning! Can not load requested doc: White spaces are required between
publicId and systemId.
And these final build errors:
BUILD FAILED
/home/jta/DB-DERBY-SVN/derby/docs/trunk/build.xml:182: The following
error occurred while executing this line:
/home/jta/DB-DERBY-SVN/derby/docs/trunk/build.xml:198: The following
error occurred while executing this line:
/home/jta/DB-DERBY-SVN/derby/docs/trunk/DITA-OT1.1.2.1/conductor.xml:209:
The following error occurred while executing this line:
/home/jta/DB-DERBY-SVN/derby/docs/trunk/DITA-OT1.1.2.1/ditatargets.xml:78:
org.apache.fop.apps.FOPException:
file:/home/jta/DB-DERBY-SVN/derby/docs/trunk/out/ref/refderby.fo:16396:40
internal-destination or external-destination must be specified in basic-link
These warnings and errors aren't very helpful. Oddly enough 'ant all'
seems to provide what looks like helpful details about specific files.
In particular two new files (rreffuncxmlexists.dita and
rreffuncxmlquery.html) both have these processing problems:
[xslt] Processing
/home/jta/DB-DERBY-SVN/derby/docs/trunk/temp/rreffuncxmlexists.dita to
/home/jta/DB-DERBY-SVN/derby/docs/trunk/out/reftemp/rreffuncxmlexists.html
[xslt]
file:/home/jta/DB-DERBY-SVN/derby/docs/trunk/DITA-OT1.1.2.1/xsl/common/output-message.xsl:43:16:
Warning! ------------------------------------------------------------------
[xslt] IDXS015E Error: (File =
/home/jta/DB-DERBY-SVN/derby/docs/trunk/src/ref/rreffuncxmlexists.dita,
Element = xref:1)
[xslt] Unknown file extension in href: http://www.w3.org/TR/xpath
[xslt] If this is a link to a non-DITA resource, set the format
attribute to match the resource (for example, 'txt', 'pdf', or 'html').
[xslt] If it's a link to a DITA resource, the file extension must
be .dita or .xml .
[xslt]
file:/home/jta/DB-DERBY-SVN/derby/docs/trunk/DITA-OT1.1.2.1/xsl/common/output-message.xsl:43:16:
Warning! ------------------------------------------------------------------
[xslt] IDXS015E Error: (File =
/home/jta/DB-DERBY-SVN/derby/docs/trunk/src/ref/rreffuncxmlexists.dita,
Element = xref:2)
[xslt] Unknown file extension in href: http://www.w3.org/TR/xquery/
[xslt] If this is a link to a non-DITA resource, set the format
attribute to match the resource (for example, 'txt', 'pdf', or 'html').
[xslt] If it's a link to a DITA resource, the file extension must
be .dita or .xml .
I hope this is helpful for isolating the problem. I think the key is to
run at least 'ant pdf', 'ant html' and 'ant monohtml'. 'ant all' is
best, especially for debugging it would seem, but I appreciate how long
that takes.
-jean
Re: Doc build fails with DERBY-1655 patch (was Re: [jira] Updated:
(DERBY-1655) Document XML functionality for 10.2)
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Andrew McIntyre wrote:
> On 8/24/06, Jean T. Anderson <jt...@bristowhill.com> wrote:
...
>
> You should still be able to see the problem when running any of the
> other ref builds: html.ref, monohtml.ref, or pdf.ref. Please let me
> know if that is the case. Also, I think what is needed are individual
> targets for the manuals, e.g. 'ant devguide' builds all three formats
> for the devguide. Not sure why noone asked for it yet, but I'll add
> that.
'ant html' reports build succeeded but there are in fact those warnings
in the output. I didn't notice that before (was tunnel visioned on the
builds that failed).
So the actual underlying problem that causes the pdf and monohtml builds
to fail might be something else entirely.
> It does take quite a while to run 'ant all' and the problem is
> twofold: one is that currently the PDFs are being generated twice,
> and the second is that the Reference Manual requires so much memory to
> build that you will most likely end up using virtual memory unless
> your machine has over a GB of memory. I will be checking in a fix for
> the first problem shortly, but there's not much I can do about the
> second one. On my main machine, it takes an hour to run 'ant all'
> without the patch, and only about 30 minutes to run with the patch.
I have 2 gig of memory and 'ant all' takes 20 minutes. Any reduction in
time would be really helpful. If there's a problem with a patch I end up
backing out and doing 'ant all' before and after applying the patch to
verify the state of my working copy really was ok, so it can really chew
up a lot of time.
-jean
Re: Doc build fails with DERBY-1655 patch (was Re: [jira] Updated: (DERBY-1655) Document XML functionality for 10.2)
Posted by Laura Stewart <sc...@gmail.com>.
What the builds are complaining about is the tagging associated with
some links to the Web. I noticed in the Derby documentation that the
incorrect tagging is being used on many Web links. The links use the
syntax phrase tag, which doesn't generate a link at all.
Doing further research, the error seems to be when either the
"external" scope is selected or the "html" format is not set.
I will update the files and run the ant ref command to see if this
fixs the problem and then resubmit a patch.
--
Laura Stewart
Re: Doc build fails with DERBY-1655 patch (was Re: [jira] Updated: (DERBY-1655) Document XML functionality for 10.2)
Posted by Andrew McIntyre <mc...@gmail.com>.
On 8/24/06, Jean T. Anderson <jt...@bristowhill.com> wrote:
>
> <snip errors/>
>
> These warnings and errors aren't very helpful.
Plus it's a case of double indirection. The error you see is not from
processing any specific dita file, but from applying a substylesheet
to the merged FO file.
> Oddly enough 'ant all'
> seems to provide what looks like helpful details about specific files.
>
> /home/jta/DB-DERBY-SVN/derby/docs/trunk/out/reftemp/rreffuncxmlexists.html
> [xslt]
> file:/home/jta/DB-DERBY-SVN/derby/docs/trunk/DITA-OT1.1.2.1/xsl/common/output-message.xsl:43:16:
> Warning! ------------------------------------------------------------------
> [xslt] IDXS015E Error: (File =
> /home/jta/DB-DERBY-SVN/derby/docs/trunk/src/ref/rreffuncxmlexists.dita,
> Element = xref:1)
> [xslt] Unknown file extension in href: http://www.w3.org/TR/xpath
> [xslt] If this is a link to a non-DITA resource, set the format
> attribute to match the resource (for example, 'txt', 'pdf', or 'html').
> [xslt] If it's a link to a DITA resource, the file extension must
> be .dita or .xml .
It's complaining about:
<xref href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</xref>
which should be either:
<xref href="http://www.w3.org/TR/xpath"
format="html">http://www.w3.org/TR/xpath</xref>
or:
<xref href="http://www.w3.org/TR/xpath.html">http://www.w3.org/TR/xpath</xref>
The first form is probably preferable. Not sure if that will fix the
overall problem, though.
> I hope this is helpful for isolating the problem. I think the key is to
> run at least 'ant pdf', 'ant html' and 'ant monohtml'. 'ant all' is
> best, especially for debugging it would seem, but I appreciate how long
> that takes.
You should still be able to see the problem when running any of the
other ref builds: html.ref, monohtml.ref, or pdf.ref. Please let me
know if that is the case. Also, I think what is needed are individual
targets for the manuals, e.g. 'ant devguide' builds all three formats
for the devguide. Not sure why noone asked for it yet, but I'll add
that.
It does take quite a while to run 'ant all' and the problem is
twofold: one is that currently the PDFs are being generated twice,
and the second is that the Reference Manual requires so much memory to
build that you will most likely end up using virtual memory unless
your machine has over a GB of memory. I will be checking in a fix for
the first problem shortly, but there's not much I can do about the
second one. On my main machine, it takes an hour to run 'ant all'
without the patch, and only about 30 minutes to run with the patch.
The patch simply eliminates the 'all' target's dependency on the 'pdf'
target, since all the dependents of the 'pdf' target will have already
been called by the various monohtml targets.
There's still room for improvement, but I'm not sure how to tackle it.
It would be great if the DITA preprocessing steps before building the
XHTML/FO could be shared between those targets so that they don't need
to occur twice. That would probably bring the time for 'ant all' in
the docs down to the sub-ten-minute range. The fix might need to be in
the DITA toolkit, unless I can find a way to chain the FO build to the
XHTML without all of the temp files being removed. Anyway, something
for a later date...
andrew