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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2010/10/29 22:00:50 UTC
[jira] Issue Comment Edited: (DERBY-4875) cross-manual xref
problems after doc build change
[ https://issues.apache.org/jira/browse/DERBY-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926435#action_12926435 ]
Rick Hillegas edited comment on DERBY-4875 at 10/29/10 4:00 PM:
----------------------------------------------------------------
Attaching derby-4875-01-aa-dontDeleteLastTemp.diff. This small patch eliminates the over-aggressive scouring of the temp_source directory. This seemed like a harmless improvement by itself, so I committed this patch at subversion revision 1028891.
I deleted the devguide directory which the docs build creates. Then I verified that I saw the FileNotFoundExceptions and the "Warning! Can not load requested doc" messages. After applying this patch and doing an "ant clobber" followed by an "ant all", I no longer see the FileNotFoundExceptions and suspect messages. I do see all of the output artifacts which I expect, including frame html, monohtml, and pdf.
Don't know if this will fix the automated build problems though. There may be other errors in there which I can't see through the blizzard of expected SEVERE warnings.
Let me know if this helps or if it just moves the problem around. Thanks.
Touches the following file:
M build.xml
was (Author: rhillegas):
Attaching derby-4875-01-aa-dontDeleteLastTemp.diff. This small patch eliminates the over-aggressive scouring of the temp_source directory. This seemed like a harmless improvement by itself, so I committed this patch at subversion
I deleted the devguide directory which the docs build creates. Then I verified that I saw the FileNotFoundExceptions and the "Warning! Can not load requested doc" messages. After applying this patch and doing an "ant clobber" followed by an "ant all", I no longer see the FileNotFoundExceptions and suspect messages. I do see all of the output artifacts which I expect, including frame html, monohtml, and pdf.
Don't know if this will fix the automated build problems though. There may be other errors in there which I can't see through the blizzard of expected SEVERE warnings.
Let me know if this helps or if it just moves the problem around. Thanks.
Touches the following file:
M build.xml
> cross-manual xref problems after doc build change
> -------------------------------------------------
>
> Key: DERBY-4875
> URL: https://issues.apache.org/jira/browse/DERBY-4875
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.7.1.0
> Reporter: Dag H. Wanvik
> Assignee: Rick Hillegas
> Attachments: derby-4875-01-aa-dontDeleteLastTemp.diff
>
>
> See thread http://old.nabble.com/Problems-with-docs-build-tt30078424.html#a30078424
> Possible cause (http://old.nabble.com/forum/Permalink.jtp?root=30078424&post=30082083&page=y)
> > After the patch, there is a new preprocessing step, that puts the
> > sources in a temp directory (from doc.properties):
> >
> > temp.source=${basedir}/temp_source
> One problem is that after preprocessing of "ref", the references to
> devguide are assumed to be present as ../devguide, cf. the generated
> dita.list (snippet below). But the way the preprocessing is currently
> done, there is only one manual at a time inside temp_source.
> Presumably, since refs were not resolved, the devguide directory is also
> missing as observed.
> Dag
> Snippet of trunk/temp/dita.list (seen while processing html.ref, inside
> target "debug" of DITA../pretargets.xml, which calls module
> DebugAndFilter):
> rrefsqlj30540.dita,../devguide/cdevcsecuregrantrevokeaccess.dita,rrefjdbc37352.dita
> and then I see this warning:
> [xslt]
> /export/home/dag/java/sb/docs/trunk/DITA-OT1.1.2.1/xsl/preprocess/topicpull.xsl:410:27:
> Warning! Can not load requested doc:
> /export/home/dag/java/sb/docs/trunk/temp/../devguide/cdevcsecuregrantrevokeaccess.dita
> (No such file or directory)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.