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 "Kim Haase (JIRA)" <ji...@apache.org> on 2006/11/06 16:52:38 UTC
[jira] Closed: (DERBY-1948) 10.2 'Working with Derby' manual
errors.
[ http://issues.apache.org/jira/browse/DERBY-1948?page=all ]
Kim Haase closed DERBY-1948.
----------------------------
Thanks very much, Micky. I'm seeing if I can close it. I thought usually the submitter of a bug could do that. I will leave it to Jean to figure out why you couldn't, since I'm relatively new to this myself.
> 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
> Fix For: 10.3.0.0, 10.2.1.8
>
> Attachments: DERBY-1948-2.diff, DERBY-1948-2.zip, DERBY-1948-3.diff, DERBY-1948-3.zip, DERBY-1948.diff, DERBY-1948.zip
>
>
> 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'.
--
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
Re: [jira] Closed: (DERBY-1948) 10.2 'Working with Derby' manual
errors.
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Kim Haase (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-1948?page=all ]
>
> Kim Haase closed DERBY-1948.
> ----------------------------
>
>
> Thanks very much, Micky. I'm seeing if I can close it. I thought usually the submitter of a bug could do that. I will leave it to Jean to figure out why you couldn't, since I'm relatively new to this myself.
Anyone with a Jira id can open an issue, but I think you need to be a
Jira developer to assign or close it.
-jean
>
>>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
>> Fix For: 10.3.0.0, 10.2.1.8
>>
>> Attachments: DERBY-1948-2.diff, DERBY-1948-2.zip, DERBY-1948-3.diff, DERBY-1948-3.zip, DERBY-1948.diff, DERBY-1948.zip
>>
>>
>>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'.
>
>