db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-4847) Errors should be displayed if using wrong CLASSPATH to make documentation target for release
Date Mon, 16 Sep 2013 23:18:53 GMT

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

Myrna van Lunteren updated DERBY-4847:

    Attachment: DERBY-4847.diff

I tried to build the docs and ran into this issue.

Attaching a patch which fails the docs build with a message when fop.jar is not on the classpath
and we're trying to build pdfs. It still builds the html files.

fop.jar appears to be the only one that is really necessary and for which there is no classpath
setting in DITA's conductor.xml.

I tried to modify the classpath for the calls to conductor.xml (it's the fo2pdf step that
does not happen if there's no fop), but conductor.xml sets the classpath specifically and
ignores what I set in build.xml. Part of ant clobber is to remove the unraveled DITA file,
so if we'd modified conductor.xml it would get thrown away next time. I thought it was cleaner
to have it fail.

I intend to commit this shortly, and backport to the 10.10 docs tree.
> Errors should be displayed if using wrong CLASSPATH to make documentation target for
> --------------------------------------------------------------------------------------------
>                 Key: DERBY-4847
>                 URL: https://issues.apache.org/jira/browse/DERBY-4847
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools, Documentation
>    Affects Versions:
>            Reporter: Lily Wei
>            Priority: Minor
>              Labels: derby_triage10_11
>         Attachments: DERBY-4847.diff
> When making Derby documentation for release, no error was prompt when wrong
version of java is being used or wrong value for CLASSPATH.
> In order to make Derby documentation, the release manager has to set CLASSPATH to include:
 fop.jar, avalon-framework-cvs-20020806.jar, and batik.jar files located in %DOC_ROOT%/trunk/lib/
for PDF output. When using wrong CLASSPATH to build pdf documentation, no error was prompt
and no PDF output was created. Error will be more intuitive that the build was not successful.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message