[
http://issues.apache.org/jira/browse/DERBY-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461818
]
Kim Haase commented on DERBY-1662:
----------------------------------
Thanks for catching this omission. I will be glad to update the docs. I have a
few questions, though.
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?
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.
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).
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?
> 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
> 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
