The output change is apparently the result of the fix to http://issues.apache.org/jira/browse/DERBY-515, and it appears on both UNIX and Windows platforms.
Kim Micky Connor wrote On 10/10/06 14:05,: > Yes, I noticed that too, but thought it was just > OS variation. > > Kim Haase (JIRA) wrote: > >> [ >> http://issues.apache.org/jira/browse/DERBY-1948?page=comments#action_12441196 >> ] >> >>Kim Haase commented on DERBY-1948: >>---------------------------------- >> >>These aren't the only errors; the output messages are not quite as described, >>either. >> >> >> >>>10.2 'Working with Derby' manual errors. >>>---------------------------------------- >>> >>> Key: DERBY-1948 >>> URL: http://issues.apache.org/jira/browse/DERBY-1948 >>> Project: Derby >>> Issue Type: Bug >>> Components: Documentation >>> Affects Versions: 10.2.1.6 >>> Environment: Under Fedora core 5 >>> Reporter: Micky Connor >>> Assigned To: Kim Haase >>> Priority: Trivial >>> >>>Going through the 10.2 'Working with Derby' manual I think I >>>have found several file path errors: >>>--Under Activity 1, the given path is >>> $DERBY_HOME/demo/toursdb/*.sql >>> but it should be >>> $DERBY_HOME/demo/programs/toursdb/*.sql >>>--Similary, under Activity 3, in section 1, the given path is >>> $DERBY_HOME/demo/workingwithderby/* >>> but it should be >>> $DERBY_HOME/demo/programs/workingwithderby/* >>>--Finally under Activity 4, section 3, the CLASSPATH given for Windows >>>refers to 'derbyclient.jar', but the UNIX version gives 'derby.jar'. The >>>necessary driver only exists in 'derbyclient.jar'. >>> >> >>
