[jira] [Updated] (DERBY-6899) Improve docs build.xml to remove CLASSPATH requirement

["Bryan Pendleton (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-6899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Pendleton updated DERBY-6899:
-----------------------------------
    Attachment: docs.diff

Actually, the docs build.xml file already has a CLASSPATH check.

However, that check is only being made when running the PDF
targets, not when running the HTML targets.

Since, in my experiments, having the FOP/Avalon/Batik classes
available in the CLASSPATH is necessary for both PDF and HTML
output, I think the simplest thing to do is just to make sure that
the "checkFOP" check is made by both the "pdf.dita" and "html.dita"
targets. The attached diff file makes that modification to build.xml.


> Improve docs build.xml to remove CLASSPATH requirement
> ------------------------------------------------------
>
>                 Key: DERBY-6899
>                 URL: https://issues.apache.org/jira/browse/DERBY-6899
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>            Reporter: Bryan Pendleton
>         Attachments: docs.diff
>
>
> As described in DERBY-6898, the docs build currently requires that
> you set a custom CLASSPATH when running Ant, otherwise you get
> build errors.
> We don't have this requirement with the main code build, so I wonder
> if we can improve the docs build.xml so that we don't need to remember
> to set a custom CLASSPATH prior to runing the docs build.
> See the derby-dev email thread from July, 2016, entitled "Need dita help"
> for more discussion about this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)