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/12/14 19:27:01 UTC
[jira] Updated: (DERBY-4847) Errors should be prompt if using wrong
CLASSPATH to make documentation target for release
[ https://issues.apache.org/jira/browse/DERBY-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-4847:
---------------------------------
Fix Version/s: (was: 10.7.1.1)
> Errors should be prompt 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
> Affects Versions: 10.6.2.1
> Reporter: Lily Wei
> Priority: Minor
>
> 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.
-
You can reply to this email to add a comment to the issue online.