db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6899) Improve docs build.xml to remove CLASSPATH requirement
Date Wed, 09 Nov 2016 02:11:58 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649554#comment-15649554
] 

ASF subversion and git services commented on DERBY-6899:
--------------------------------------------------------

Commit 1768814 from [~bryanpendleton] in branch 'docs/trunk'
[ https://svn.apache.org/r1768814 ]

DERBY-6899: Improve docs build.xml to check for correct CLASSPATH

This change modifies the html.dita target to invoke the check.fop
classpath-checking target, just as is currently done for the
pdf.dita target, because some of the code paths that html.dita
takes also require that the fop/avalon/batik classes are present.

> 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)

Mime
View raw message