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-4847) Errors should be displayed if using wrong CLASSPATH to make documentation target for release
Date Tue, 17 Sep 2013 00:40:51 GMT

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

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

Commit 1523858 from [~myrna] in branch 'docs/trunk'
[ https://svn.apache.org/r1523858 ]

DERBY-4847; Errors should be displayed if using wrong CLASSPATH to make documentation target
for release
  Making the build fail and displaying a message if fop.jar is missing from the CLASSPATH
and an attempt is made to build pdf files.
                
> Errors should be displayed if using wrong CLASSPATH to make documentation target for
release
> --------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4847
>                 URL: https://issues.apache.org/jira/browse/DERBY-4847
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools, Documentation
>    Affects Versions: 10.6.2.1
>            Reporter: Lily Wei
>            Priority: Minor
>              Labels: derby_triage10_11
>         Attachments: DERBY-4847.diff
>
>
> When making Derby documentation for 10.6.2.1 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

Mime
View raw message