You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by rh...@apache.org on 2018/11/20 16:42:57 UTC

svn commit: r1847027 - in /db/derby/docs/trunk/src/getstart: getstartderby.ditamap rgsderbyrunjarsyntax.dita rgslib46043.dita tgs26250.dita tgsrunningdblook.dita tgsrunningij.dita tgsrunningsysinfo.dita tgsruntoolsutils.dita tgssetupjavaenvir.dita

Author: rhillegas
Date: Tue Nov 20 16:42:57 2018
New Revision: 1847027

URL: http://svn.apache.org/viewvc?rev=1847027&view=rev
Log:
DERBY-6980: Adjust Getting Started Guide to account for the modularization changes introduced by work on DERBY-6945; commit derby-6980-07-aa-gettingStartedGuide.diff.

Modified:
    db/derby/docs/trunk/src/getstart/getstartderby.ditamap
    db/derby/docs/trunk/src/getstart/rgsderbyrunjarsyntax.dita
    db/derby/docs/trunk/src/getstart/rgslib46043.dita
    db/derby/docs/trunk/src/getstart/tgs26250.dita
    db/derby/docs/trunk/src/getstart/tgsrunningdblook.dita
    db/derby/docs/trunk/src/getstart/tgsrunningij.dita
    db/derby/docs/trunk/src/getstart/tgsrunningsysinfo.dita
    db/derby/docs/trunk/src/getstart/tgsruntoolsutils.dita
    db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita

Modified: db/derby/docs/trunk/src/getstart/getstartderby.ditamap
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/getstartderby.ditamap?rev=1847027&r1=1847026&r2=1847027&view=diff
==============================================================================
--- db/derby/docs/trunk/src/getstart/getstartderby.ditamap (original)
+++ db/derby/docs/trunk/src/getstart/getstartderby.ditamap Tue Nov 20 16:42:57 2018
@@ -127,7 +127,7 @@ limitations under the License.
 </relrow>
 <relrow>
 <relcell>
-<topicref href="tgs26250.dita" navtitle="Manually setting the CLASSPATH environment variable">
+<topicref href="tgs26250.dita" navtitle="Manually setting the CLASSPATH/MODULEPATH environment variables">
 </topicref>
 </relcell>
 <relcell></relcell>

Modified: db/derby/docs/trunk/src/getstart/rgsderbyrunjarsyntax.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/rgsderbyrunjarsyntax.dita?rev=1847027&r1=1847026&r2=1847027&view=diff
==============================================================================
--- db/derby/docs/trunk/src/getstart/rgsderbyrunjarsyntax.dita (original)
+++ db/derby/docs/trunk/src/getstart/rgsderbyrunjarsyntax.dita Tue Nov 20 16:42:57 2018
@@ -78,7 +78,10 @@ environment variable to set CLASSPATH va
 If you want to run the <codeph>ij</codeph> tool with a custom classpath, 
 you cannot use the <codeph>-jar</codeph> argument. Instead, you have to 
 use the full class name to start the <codeph>ij</codeph> tool 
-(<codeph>java org.apache.derby.tools.ij</codeph>). </p>
+(<codeph>java org.apache.derby.tools.ij</codeph>).
+In addition, you cannot use any of the module-aware command line switches such as
+<i>-p</i>, <i>-m</i>, and <i>--add-modules</i>.
+</p>
 
 <p>See <xref href="tgs26250.dita#tgs26250"/> for more information
 about setting up the classpath and running the <codeph>ij</codeph> tool.</p>

Modified: db/derby/docs/trunk/src/getstart/rgslib46043.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/rgslib46043.dita?rev=1847027&r1=1847026&r2=1847027&view=diff
==============================================================================
--- db/derby/docs/trunk/src/getstart/rgslib46043.dita (original)
+++ db/derby/docs/trunk/src/getstart/rgslib46043.dita Tue Nov 20 16:42:57 2018
@@ -20,7 +20,7 @@ limitations under the License.
 -->
 <reference id="rgslib46043" xml:lang="en-us">
 <title>Libraries provided by Derby</title>
-<shortdesc>This section shows the different libraries used by
+<shortdesc>This section shows the different libraries (modules) used by
 <ph conref="../conrefs.dita#prod/productshortname"></ph> and their
 purposes.</shortdesc>
 <prolog><metadata>
@@ -31,6 +31,32 @@ purposes.</shortdesc>
 </metadata></prolog>
 <refbody>
 <section>
+
+<p>The following table shows the
+<ph conref="../conrefs.dita#prod/productshortname"></ph> shared library. This module
+is required by all Derby configurations.</p>
+<table>
+<title>Engine library</title>
+<desc>This table lists the <ph conref="../conrefs.dita#prod/productshortname"></ph> shared library and describes its uses.</desc>
+<tgroup cols="2" colsep="1" rowsep="1">
+<colspec colname="col1" colnum="1" colwidth="35*"/>
+<colspec colname="col2" colnum="2" colwidth="65*"/>
+<thead>
+<row valign="bottom">
+<entry colname="col1">Library Name</entry>
+<entry colname="col2">Use</entry>
+</row>
+</thead>
+<tbody>
+<row>
+<entry colname="col1"><codeph>derbyshared.jar</codeph></entry>
+<entry colname="col2">This module is required by all configurations, regardless of whether you are
+running an embedded engine, a network server, a remote client, or the database tools.</entry>
+</row>
+</tbody>
+</tgroup>
+</table>
+
 <p>The following table shows the
 <ph conref="../conrefs.dita#prod/productshortname"></ph> engine library.</p>
 <table>
@@ -55,9 +81,10 @@ the server.</p></entry>
 </tbody>
 </tgroup>
 </table>
-<p>For embedded environments, you need a library in the classpath to use
-a tool. For a client/server environment, you need a library on the client
-only. The following table shows the tools libraries.</p>
+
+<p>For embedded environments, you need another module in the classpath/modulepath in order to use
+the tools. For a client/server environment, you need that library on the client
+only. The following table shows the tools module.</p>
 <table>
 <title>Tools libraries</title>
 <desc>This table lists the <ph conref="../conrefs.dita#prod/productshortname"></ph> tools libraries and describes their uses.</desc>
@@ -75,7 +102,8 @@ only. The following table shows the tool
 <entry colname="col1"><codeph>derbytools.jar</codeph></entry>
 <entry colname="col2">Required for running all the
 <ph conref="../conrefs.dita#prod/productshortname"></ph> tools (such as
-<codeph>ij</codeph>, <codeph>dblook</codeph>, and import/export).</entry>
+<codeph>ij</codeph>, <codeph>dblook</codeph>, and import/export). This module
+is also required if you are running a network server.</entry>
 </row>
 <row>
 <entry colname="col1"><codeph>derbyrun.jar</codeph></entry>
@@ -87,7 +115,7 @@ only. The following table shows the tool
 </table>
 <p>The following table shows the
 <ph conref="../conrefs.dita#prod/productshortname"></ph> Network Server
-library.</p>
+library. You need this module as well as the shared, engine, and tools modules.</p>
 <table>
 <title>Network Server library</title>
 <desc>This table lists the <ph conref="../conrefs.dita#prod/productshortname"></ph> Network Server library and describes its uses.</desc>
@@ -218,6 +246,53 @@ Traditional Chinese locale.</entry>
 </tbody>
 </tgroup>
 </table>
+
+<p>To summarize, the following table shows the libraries (modules) which are required
+for each
+<ph conref="../conrefs.dita#prod/productshortname"></ph> configuration.</p>
+<table>
+<title>Required libraries</title>
+<desc>This table lists the <ph conref="../conrefs.dita#prod/productshortname"></ph> modules required for each configuration.</desc>
+<tgroup cols="2" colsep="1" rowsep="1">
+<colspec colname="col1" colnum="1" colwidth="35*"/>
+<colspec colname="col2" colnum="2" colwidth="65*"/>
+<thead>
+<row valign="bottom">
+<entry colname="col1">Configuration</entry>
+<entry colname="col2">Required modules</entry>
+</row>
+</thead>
+<tbody>
+
+<row>
+<entry colname="col1"><codeph>Remote client</codeph></entry>
+<entry colname="col2">derbyclient.jar, derbyshared.jar</entry>
+</row>
+
+<row>
+<entry colname="col1"><codeph>Embedded engine</codeph></entry>
+<entry colname="col2">derby.jar, derbyshared.jar</entry>
+</row>
+
+<row>
+<entry colname="col1"><codeph>Network server</codeph></entry>
+<entry colname="col2">derbynet.jar, derbytools.jar, derby.jar, derbyshared.jar</entry>
+</row>
+
+<row>
+<entry colname="col1"><codeph>Embedded tools</codeph></entry>
+<entry colname="col2">derbytools.jar, derby.jar, derbyshared.jar</entry>
+</row>
+
+<row>
+<entry colname="col1"><codeph>Convenient startup</codeph></entry>
+<entry colname="col2">derbyrun.jar, derbynet.jar, derbytools.jar, derby.jar, derbyshared.jar</entry>
+</row>
+
+</tbody>
+</tgroup>
+</table>
+
 </section>
 </refbody>
 </reference>

Modified: db/derby/docs/trunk/src/getstart/tgs26250.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgs26250.dita?rev=1847027&r1=1847026&r2=1847027&view=diff
==============================================================================
--- db/derby/docs/trunk/src/getstart/tgs26250.dita (original)
+++ db/derby/docs/trunk/src/getstart/tgs26250.dita Tue Nov 20 16:42:57 2018
@@ -19,8 +19,8 @@ See the License for the specific languag
 limitations under the License.
 -->
 <task id="tgs26250" xml:lang="en-us">
-<title>Manually setting the CLASSPATH environment variable</title>
-<shortdesc>You can set the CLASSPATH environment variable in the operating
+<title>Manually setting the CLASSPATH/MODULEPATH environment variables</title>
+<shortdesc>You can set the CLASSPATH and MODULEPATH environment variables in the operating
 system either temporarily, permanently, or at run time when you start your
 Java application and the JVM. </shortdesc>
 <prolog><metadata>
@@ -31,32 +31,30 @@ variables<indexterm>CLASSPATH</indexterm
 </metadata></prolog>
 <taskbody>
 <context><p>The classpath is a list of the class libraries that are needed
-by the JVM and other Java applications to run your program. There are scripts
+by the JVM and other Java applications to run your program.
+Similarly, the modulepath is a corresponding list of Java modules needed by your program.
+There are scripts
 that are included with <ph conref="../conrefs.dita#prod/productshortname"></ph> that
-can set up the classpath to run the <ph conref="../conrefs.dita#prod/productshortname"></ph> tools. </p><p>If
+can set up the classpath/modulepath to run the <ph conref="../conrefs.dita#prod/productshortname"></ph> tools. </p><p>If
 you want to call the <ph conref="../conrefs.dita#prod/productshortname"></ph> tools
 directly using Java and not using the scripts, you must manually set the CLASSPATH
-environment variable.</p><p>In most development environments, it is best to
-temporarily set the CLASSPATH environment variable in the command line shell
+environment variable or manually declare a modulepath.</p><p>In most development environments, it is best to
+temporarily set these variables in the command line shell
 where you are entering commands.</p><p> <ph conref="../conrefs.dita#prod/productshortname"></ph> provides
 several scripts in the <ph conref="../conrefs.dita#prod/productinstallpath"></ph><filepath>/bin</filepath> directory
-to help you set your classpath quickly. These scripts are: <dl><dlentry>
+to help you set your classpath/modulepath quickly. These scripts are: <dl><dlentry>
 <dt>setEmbeddedCP</dt>
-<dd>Use the <cmdname>setEmbeddedCP</cmdname> script to set the classpath when
-the database engine is used in embedded mode. This script adds the <filepath>derby.jar</filepath>, <filepath>derbytools.jar</filepath> and <filepath>derbyoptionaltools.jar</filepath> files
-to the classpath. </dd>
+<dd>Use the <cmdname>setEmbeddedCP</cmdname> script to set CLASSPATH and MODULEPATH when
+the database engine is used in embedded mode.</dd>
 </dlentry><dlentry>
 <dt>setNetworkServerCP</dt>
-<dd>Use the <cmdname>setNetworkServerCP</cmdname> script to set the classpath
-when you want to start the network server. This script adds the <filepath>derbynet.jar</filepath> file
-to the classpath. </dd>
+<dd>Use the <cmdname>setNetworkServerCP</cmdname> script to set CLASSPATH and MODULEPATH
+when you want to start the network server.</dd>
 </dlentry><dlentry>
 <dt>setNetworkClientCP</dt>
-<dd>Use the <cmdname>setNetworkClientCP</cmdname> script to set the classpath
-when you want to access databases using the network client. This script adds
-the <filepath>derbyclient.jar</filepath>, <filepath>derbytools.jar</filepath> and <filepath>derbyoptionaltools.jar</filepath> files
-to the classpath. </dd>
-</dlentry></dl></p><p>To set the classpath temporarily, run the script that
+<dd>Use the <cmdname>setNetworkClientCP</cmdname> script to set CLASSPATH and MODULEPATH
+when you want to access databases using the network client.</dd>
+</dlentry></dl></p><p>To set the classpath and modulepath temporarily, run the script that
 is appropriate for your environment every time that you open a new command
 window.</p>
 <p>
@@ -68,12 +66,12 @@ window.</p>
     command to ensure that the script
     is run in the calling shell's environment. Otherwise, when a script
     is run, it launches a new shell for that script.
-    The CLASSPATH is set within that shell.
+    The CLASSPATH and MODULEPATH variables are set within that shell.
     Once the script is complete, that
     shell exits and you are returned to your shell.
-    The CLASSPATH is changed only for the shell that the script was
+    CLASSPATH/MODULEPATH are changed only for the shell that the script was
     running in.
-    The CLASSPATH in your shell is unchanged. 
+    The CLASSPATH and MODULEPATH variables in your shell are unchanged. 
 </p>
 <p>
     The UNIX shell scripts are known to run successfully in the Bash shell,
@@ -91,7 +89,7 @@ sh-2.05b$ echo $CLASSPATH
 sh-2.05b$ DERBY_HOME=/derby/db-derby-10.X.Y.0-bin
 sh-2.05b$ . $DERBY_HOME/bin/setEmbeddedCP
 sh-2.05b$ echo $CLASSPATH
-/derby/db-derby-10.X.Y.0-bin/lib/derby.jar:/derby/db-derby-10.X.Y.0-bin/lib/derbytools.jar:/derby/db-derby-10.X.Y.0-bin/lib/derbyoptionaltools.jar:
+/derby/db-derby-10.X.Y.0-bin/lib/derbyshared.jar:/derby/db-derby-10.X.Y.0-bin/lib/derby.jar:/derby/db-derby-10.X.Y.0-bin/lib/derbytools.jar:/derby/db-derby-10.X.Y.0-bin/lib/derbyoptionaltools.jar:
 sh-2.05b$ java org.apache.derby.tools.ij
 ij version 10.X
 ij> quit;
@@ -112,7 +110,7 @@ C:\derby\db-derby-10.X.Y.0-bin\bin>echo
 C:\derby\db-derby-10.X.Y.0-bin\bin>set DERBY_HOME=C:\derby\db-derby-10.X.Y.0-bin
 C:\derby\db-derby-10.X.Y.0-bin\bin>setEmbeddedCP.bat
 C:\derby\db-derby-10.X.Y.0-bin\bin>echo %CLASSPATH%
-C:\derby\DB-DERBY-10.X.Y.0-bin\lib\derby.jar;C:\derby\DB-DERBY-10.X.Y.0-bin\lib\derbytools.jar;C:\derby\DB-DERBY-10.X.Y.0-bin\lib\derbyoptionaltools.jar;
+C:\derby\DB-DERBY-10.X.Y.0-bin\lib\derbyshared.jar;C:\derby\DB-DERBY-10.X.Y.0-bin\lib\derby.jar;C:\derby\DB-DERBY-10.X.Y.0-bin\lib\derbytools.jar;C:\derby\DB-DERBY-10.X.Y.0-bin\lib\derbyoptionaltools.jar;
 C:\derby\db-derby-10.X.Y.0-bin\bin>java org.apache.derby.tools.ij
 ij version 10.X
 ij> quit;

Modified: db/derby/docs/trunk/src/getstart/tgsrunningdblook.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgsrunningdblook.dita?rev=1847027&r1=1847026&r2=1847027&view=diff
==============================================================================
--- db/derby/docs/trunk/src/getstart/tgsrunningdblook.dita (original)
+++ db/derby/docs/trunk/src/getstart/tgsrunningdblook.dita Tue Nov 20 16:42:57 2018
@@ -50,6 +50,7 @@ script. The methods are listed in the fo
 </row>
 </thead>
 <tbody>
+
 <row>
 <entry colname="col1">Run <codeph>dblook</codeph> as a standalone command.</entry>
 <entry colname="col2">Use this method if you are relatively new to the Java
@@ -64,6 +65,7 @@ programming language and new to
 variables, including the CLASSPATH, and runs the <codeph>dblook</codeph>
 utility.</p></entry>
 </row>
+
 <row>
 <entry colname="col1">Run <codeph>dblook</codeph> using the jar file that is
 located in the directory where <codeph>dblook</codeph> resides.</entry>
@@ -78,6 +80,7 @@ before you can run the <codeph>dblook</c
 <p>On Windows, the command is:</p>
 <codeblock>java [options] -jar %DERBY_HOME%\lib\derbyrun.jar dblook -d <i>connectionURL</i> [<i>options</i>]</codeblock></entry>
 </row>
+
 <row>
 <entry colname="col1">Run <codeph>dblook</codeph> using the
 <codeph>java</codeph> command.</entry>
@@ -91,6 +94,31 @@ execution PATH.</entry>
 <codeph>java</codeph> command. For example:
 <codeblock>java org.apache.derby.tools.dblook -d <i>connectionURL</i> [<i>options</i>]</codeblock></entry>
 </row>
+
+<row>
+<entry colname="col1">Run <codeph>dblook</codeph> using the
+<codeph>java</codeph> command using a modulepath.</entry>
+<entry colname="col2">Use this method if you are familiar with both the Java
+programming language and
+<ph conref="../conrefs.dita#prod/productshortname"></ph>, have already
+added the location of the <codeph>java</codeph> executable file to your command
+execution PATH, and expect to run Derby with a modulepath.</entry>
+<entry colname="col3">You must set your MODULEPATH. Use the steps specified in
+<xref href="tgs26250.dita#tgs26250"></xref>. Then specify the tools module and the dblook class name in the
+<codeph>java</codeph> command.
+<p>On UNIX, the command is:</p>
+<codeblock>java -p $MODULEPATH \
+  -m org.apache.derby.tools/org.apache.derby.tools.dblook \
+  -d connectionURL [options]
+</codeblock>
+<p>On Windows, the command is:</p>
+<codeblock>java -p %MODULEPATH% ^
+  -m org.apache.derby.tools/org.apache.derby.tools.dblook ^
+  -d connectionURL [options]
+</codeblock>
+</entry>
+</row>
+
 </tbody>
 </tgroup>
 </table> 

Modified: db/derby/docs/trunk/src/getstart/tgsrunningij.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgsrunningij.dita?rev=1847027&r1=1847026&r2=1847027&view=diff
==============================================================================
--- db/derby/docs/trunk/src/getstart/tgsrunningij.dita (original)
+++ db/derby/docs/trunk/src/getstart/tgsrunningij.dita Tue Nov 20 16:42:57 2018
@@ -47,6 +47,7 @@ script. The methods are listed in the fo
 </row>
 </thead>
 <tbody>
+
 <row>
 <entry colname="col1">Run <codeph>ij</codeph> as a standalone command.</entry>
 <entry colname="col2">Use this method if you are relatively new to the Java
@@ -65,6 +66,7 @@ directory to your PATH environment varia
 variables, including the CLASSPATH, and starts the <codeph>ij</codeph>
 tool.</p></entry>
 </row>
+
 <row>
 <entry colname="col1">Run <codeph>ij</codeph> using the jar file that is located
 in the directory where <codeph>ij</codeph> resides.</entry>
@@ -79,6 +81,7 @@ before you can run the <codeph>ij</codep
 <p>On Windows, the command is:</p>
 <codeblock>java -jar %DERBY_HOME%\lib\derbyrun.jar ij </codeblock></entry>
 </row>
+
 <row>
 <entry colname="col1">Run <codeph>ij</codeph> using the <codeph>java</codeph>
 command.</entry>
@@ -92,6 +95,29 @@ execution PATH.</entry>
 <codeph>java</codeph> command. For example:
 <codeblock>java org.apache.derby.tools.ij</codeblock></entry>
 </row>
+
+<row>
+<entry colname="col1">Run <codeph>ij</codeph> using the <codeph>java</codeph>
+command with a modulepath.</entry>
+<entry colname="col2">Use this method if you are familiar with both the Java
+programming language and
+<ph conref="../conrefs.dita#prod/productshortname"></ph>, have already
+added the location of the <codeph>java</codeph> executable file to your command
+execution PATH, and expect to run Derby via the modulepath.</entry>
+<entry colname="col3">You must set your MODULEPATH. Use the steps specified in
+<xref href="tgs26250.dita#tgs26250"></xref>. Then specify the tools module and the ij class name in the
+<codeph>java</codeph> command.
+<p>On UNIX, the command is:</p>
+<codeblock>java -p $MODULEPATH \
+  -m org.apache.derby.tools/org.apache.derby.tools.ij
+</codeblock>
+<p>On Windows, the command is:</p>
+<codeblock>java -p %MODULEPAT% ^
+  -m org.apache.derby.tools/org.apache.derby.tools.ij
+</codeblock>
+</entry>
+</row>
+
 </tbody>
 </tgroup>
 </table> 

Modified: db/derby/docs/trunk/src/getstart/tgsrunningsysinfo.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgsrunningsysinfo.dita?rev=1847027&r1=1847026&r2=1847027&view=diff
==============================================================================
--- db/derby/docs/trunk/src/getstart/tgsrunningsysinfo.dita (original)
+++ db/derby/docs/trunk/src/getstart/tgsrunningsysinfo.dita Tue Nov 20 16:42:57 2018
@@ -46,6 +46,7 @@ the following table.</p>
 </row>
 </thead>
 <tbody>
+
 <row>
 <entry colname="col1">Run <codeph>sysinfo</codeph> as a standalone command.</entry>
 <entry colname="col2">Use this method if you are relatively new to the Java
@@ -60,6 +61,7 @@ programming language and new to
 variables, including the CLASSPATH, and runs the <codeph>sysinfo</codeph>
 utility.</p></entry>
 </row>
+
 <row>
 <entry colname="col1">Run <codeph>sysinfo</codeph> using the jar file that is
 located in the directory where <codeph>sysinfo</codeph> resides.</entry>
@@ -74,6 +76,7 @@ before you can run the <codeph>sysinfo</
 <p>On Windows, the command is:</p>
 <codeblock>java [options] -jar %DERBY_HOME%\lib\derbyrun.jar sysinfo</codeblock></entry>
 </row>
+
 <row>
 <entry colname="col1">Run <codeph>sysinfo</codeph> using the
 <codeph>java</codeph> command.</entry>
@@ -87,6 +90,29 @@ execution PATH.</entry>
 <codeph>java</codeph> command. For example:
 <codeblock>java org.apache.derby.tools.sysinfo</codeblock></entry>
 </row>
+
+<row>
+<entry colname="col1">Run <codeph>sysinfo</codeph> using the
+<codeph>java</codeph> command with a modulepath.</entry>
+<entry colname="col2">Use this method if you are familiar with both the Java
+programming language and
+<ph conref="../conrefs.dita#prod/productshortname"></ph>, have already
+added the location of the <codeph>java</codeph> executable file to your command
+execution PATH, and expect to run Derby via a modulepath.</entry>
+<entry colname="col3">You must set your MODULEPATH variable. Use the steps specified in
+<xref href="tgs26250.dita#tgs26250"></xref>. Then specify the tools module and the sysinfo class name in the
+<codeph>java</codeph> command.
+<p>On UNIX, the command is:</p>
+<codeblock>java -p $MODULEPATH \
+  -m org.apache.derby.tools/org.apache.derby.tools.sysinfo
+</codeblock>
+<p>On Windows, the command is:</p>
+<codeblock>java -p %MODULEPATH% ^
+  -m org.apache.derby.tools/org.apache.derby.tools.sysinfo
+</codeblock>
+</entry>
+</row>
+
 </tbody>
 </tgroup>
 </table>

Modified: db/derby/docs/trunk/src/getstart/tgsruntoolsutils.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgsruntoolsutils.dita?rev=1847027&r1=1847026&r2=1847027&view=diff
==============================================================================
--- db/derby/docs/trunk/src/getstart/tgsruntoolsutils.dita (original)
+++ db/derby/docs/trunk/src/getstart/tgsruntoolsutils.dita Tue Nov 20 16:42:57 2018
@@ -101,9 +101,9 @@ of setting up the execution environment<
 <codeph>JAVA_HOME\bin</codeph>) in the PATH environment variable</li>
 <li>You must know the full package name for the Java class that supports the
 tool</li>
-<li>The CLASSPATH environment variable must be set to include the required
+<li>The CLASSPATH or MODULEPATH environment variable must be set to include the required
 JAR files</li>
-</ul><p>For details on setting the CLASSPATH, see 
+</ul><p>For details on setting the CLASSPATH/MODULEPATH, see 
 <xref href="tgs26250.dita#tgs26250"></xref>.</p></entry>
 </row>
 </tbody>

Modified: db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita?rev=1847027&r1=1847026&r2=1847027&view=diff
==============================================================================
--- db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita (original)
+++ db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita Tue Nov 20 16:42:57 2018
@@ -40,7 +40,7 @@ the <ph conref="../conrefs.dita#prod/pro
 variable so that you can use the command examples
 that are presented in this manual.  Adding the <ph conref="../conrefs.dita#prod/productshortname"></ph> scripts
 directory to your command execution PATH makes the scripts easier to use and
-enables you to use the script examples in this manual.  The CLASSPATH environment
+enables you to use the script examples in this manual.  The CLASSPATH or MODULEPATH environment
 variable must be set if you are using <ph conref="../conrefs.dita#prod/productshortname"></ph> in
 a Java program or executing the tools using the <codeph>java</codeph> command.<p>The
 steps below show you how to set the environment variables in a command window.