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

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

Kim asked: "It seems as if there are now two main preferred ways to run the 
tools:

1) Add the $DERBY_HOME/bin directory to your PATH and run the commands using 
only the command name -- for example,

  ij

2) Don't modify your path and run the commands using the jar file -- for 
example,

  java -jar $DERBY_HOME/lib/derbyrun.jar ij

Is that correct? What would be the advantage of using each of these?"

The first method requires less typing, so if you are running the tools a lot, 
it is easier on the fingers. Plus many people are just used to using scripts to 
run tools. The second doesn't require that you set anything in your environment 
before running one of the tools. So, it's probably better for people who run 
the tools less frequently, don't want to alter their environment settings, or 
for power users that want the quickest route from downloading a distribution to 
running the tools.

and: "It seems to be also possible to add $DERBY_HOME/lib/derbyrun.jar to your 
CLASSPATH and then use the command

  java org.apache.derby.tools.ij

Should we continue to document this as a preferred method? It seems more 
cumbersome. "

This is an equally valid way to start the tools, and probably appeals to a 
different sort of power user that maintains several Derby environments and has 
scripts to set up the environment for each one. All three are equally valid, 
and I don't think we need to necessarily promote one over the other. Although, 
a couple of people on derby-dev have recently expressed their personal 
preference for the java -jar method.

and: "What is the "server" tool (invoked by "java -jar derbyrun.jar server"? 
Where do we document it? It doesn't seem to be a tool like the others (I can't 
find the class in any of the jar files). "

server is an alias for org.apache.derby.drda.NetworkServerControl. 

and: "Some manuals also document using the scripts in the 
$DERBY_HOME/frameworks/NetworkServer/bin/ and 
$DERBY_HOME/frameworks/embedded/bin directories. Since we're saying in the 
current docs that these will be deprecated in the future, should the manuals 
stop describing how to use these scripts and instead describe how to use the 
ones in the $DERBY_HOME/bin directory?"

I am planning on removing these references as a part of DERBY-1709, unless 
someone beats me to it.

> Document derbyrun.jar
> ---------------------
>
>                 Key: DERBY-1662
>                 URL: http://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
>
> 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.
-
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

        

Reply via email to