db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1662) Document derbyrun.jar
Date Wed, 07 Feb 2007 22:52:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471138
] 

Andrew McIntyre commented on DERBY-1662:
----------------------------------------

Hi Kim,

This is really close. To answer your questions:

rtools1003161: yes, that works. I think a pointer to the dev guide is all that is needed,
since there is extensive discussion of the topic there.

ttoolsij11815: right, the sentence just needed to be removed since it was no longer correct.

And for the new changes included in the patch:

tadminappschangingyourclasspath:
- derbynet.jar description should be something like: "This jar file contains the Network Server
code. It must be in your classpath to start the Network Server."
- The derby.jar description should be changed to something like: "This jar file contains the
Derby database engine code. It must be in the classpath in order for the network server to
access Derby databases. derby.jar is included in the Class-Path attribute of derbynet.jar's
manifest. If you have derbynet.jar in the classpath and derby.jar is in the same directory
as derbynet.jar, it is not necessary to include it explicitly."
- For derbyclient.jar: The first sentence is sort of redundant. The rest should probably be
changed to something along the lines of: "This jar file contains the Derby Network Client
JDBC driver that is necessary for communication with the Network Server. It must be in the
classpath of the application on the client side in order to access Derby over a network."

tadmincbdjhhfd: this looks great!

tadminconfig815768: for the network server, the correct sysinfo commands should be: 'java
-jar $DERBY_HOME/lib/derbyrun.jar server sysinfo' and 'java org.apache.derby.drda.NetworkServerControl
sysinfo'

tadminconfigsysteminformation: sysinfo(.bat) will no longer give you the network server sysinfo.
You can get this information via script by running 'NetworkServerControl(.bat) sysinfo'

The rest is good.

If you'd like to tackle the documentation part of DERBY-1709, that would be great. I'll gladly
review your patch.

> Document derbyrun.jar
> ---------------------
>
>                 Key: DERBY-1662
>                 URL: https://issues.apache.org/jira/browse/DERBY-1662
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.2.1.6
>            Reporter: David Van Couvering
>         Assigned To: Kim Haase
>            Priority: Minor
>         Attachments: cgsusingtoolsutils.html, DERBY-1662-2.diff, DERBY-1662-2.zip, DERBY-1662-3.diff,
DERBY-1662-3.zip, DERBY-1662.diff, tadmincbdjhhfd.html
>
>
> The documentation for ij in the Tools Guide only describes how to start ij the old way.
 It should also describe how to start it using derbyrun.jar. 
> I wonder if the same is true for the other tools, although I haven't investigated.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message