[ http://issues.apache.org/jira/browse/DERBY-1470?page=comments#action_12426436 ] Daniel John Debrunner commented on DERBY-1470: ----------------------------------------------
I would say step 4) above is wrong, the up front introduction examples should not be giving the impression that derby.jar is required on the client side. The alternative would be to have derbytools.jar, which is logical to have on the client. Adding sysinfo to the client jar seems to make sense as well. > Correct instructions in demo html file demo\simple\example.html > --------------------------------------------------------------- > > Key: DERBY-1470 > URL: http://issues.apache.org/jira/browse/DERBY-1470 > Project: Derby > Issue Type: Bug > Components: Demos/Scripts > Affects Versions: 10.2.0.0, 10.1.3.1 > Environment: Any platform on which we support derby > Reporter: Ramandeep Kaur > Assigned To: Ramandeep Kaur > Priority: Minor > Fix For: 10.2.0.0 > > Attachments: derby-1470-alt.diff, DERBY-1470.diff > > > In file demo\simple\example.html, under section "Next run the SimpleApp demo > in Derby client mode:", step 5 > "java org.apache.derby.tools.sysinfo -cp client SimpleApp.class" gives the > following error: > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/derby/tools/sysinfo > The above error is given because step 4 instructs to set path as following: > export CLASSPATH=.:${DERBY_INSTALL}/lib/derbyclient.jar > Now as neither derby.jar or derbytool.jar is been added to the above > classpath, sysinfo file not found. > Step 4 should instruct to set up path as following: > export > CLASSPATH=.:${DERBY_INSTALL}/lib/derbyclient.jar:${DERBY_INSTALL}/lib/derby.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
