[DERBY-4847] Errors should be displayed if using wrong CLASSPATH to make documentation target for release

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.6.2.1
• Fix Version/s: 10.10.2.0, 10.11.1.1
• Component/s: Build tools, Documentation
• Labels: derby_triage10_11
• Urgency: Normal
• Issue & fix info: Newcomer
• Assignee: Myrna van Lunteren
• Reporter: Lily Wei
• Created: 14/Oct/10 01:39
• Updated: 21/Jan/15 00:23
• Resolved: 17/Sep/13 16:01

Description

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.

Issue Links

• is part of: DERBY-4850 Master JIRA for improving release processes