18 .\" |
17 .\" |
19 .\" Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA |
18 .\" Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA |
20 .\" or visit www.oracle.com if you need additional information or have any |
19 .\" or visit www.oracle.com if you need additional information or have any |
21 .\" questions. |
20 .\" questions. |
22 .\" |
21 .\" |
23 .\" Arch: generic |
22 .\" Automatically generated by Pandoc 2.3.1 |
24 .\" Software: JDK 8 |
23 .\" |
25 .\" Date: 21 November 2013 |
24 .TH "RMIC" "1" "2018" "JDK 13" "JDK Commands" |
26 .\" SectDesc: Remote Method Invocation (RMI) Tools |
25 .hy |
27 .\" Title: rmic.1 |
26 .SH NAME |
28 .\" |
27 .PP |
29 .if n .pl 99999 |
28 rmic \- generate stub and skeleton class files using the Java Remote |
30 .TH rmic 1 "21 November 2013" "JDK 8" "Remote Method Invocation (RMI) Tools" |
29 Method Protocol (JRMP) |
31 .\" ----------------------------------------------------------------- |
30 .SH SYNOPSIS |
32 .\" * Define some portability stuff |
31 .PP |
33 .\" ----------------------------------------------------------------- |
32 \f[CB]rmic\f[R] [\f[I]options\f[R]] |
34 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
33 \f[I]package\-qualified\-class\-names\f[R] |
35 .\" http://bugs.debian.org/507673 |
34 .TP |
36 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html |
35 .B \f[I]options\f[R] |
37 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
36 This represent the command\-line \f[CB]options\f[R] for the\f[CB]rmic\f[R] |
38 .ie \n(.g .ds Aq \(aq |
37 compiler. |
39 .el .ds Aq ' |
38 See \f[B]Options for the rmic Compiler\f[R]. |
40 .\" ----------------------------------------------------------------- |
39 .RS |
41 .\" * set default formatting |
40 .RE |
42 .\" ----------------------------------------------------------------- |
41 .TP |
43 .\" disable hyphenation |
42 .B \f[I]package\-qualified\-class\-names\f[R] |
44 .nh |
43 Class names that include their packages, for example, |
45 .\" disable justification (adjust text to left margin only) |
44 \f[CB]java.awt.Color\f[R]. |
46 .ad l |
45 .RS |
47 .\" ----------------------------------------------------------------- |
46 .RE |
48 .\" * MAIN CONTENT STARTS HERE * |
47 .SH DESCRIPTION |
49 .\" ----------------------------------------------------------------- |
48 .PP |
50 |
49 \f[B]Deprecation Note:\f[R] The rmic tool has been deprecated and is |
51 .SH NAME |
50 subject to removal in a future release. |
52 rmic \- Generates stub, skeleton, and tie classes for remote objects that use the Java Remote Method Protocol (JRMP) or Internet Inter-Orb protocol (IIOP)\&. Also generates Object Management Group (OMG) Interface Definition Language (IDL) |
51 Support for static generation of Java Remote Method Protocol (JRMP) |
53 .SH SYNOPSIS |
52 stubs and skeletons has been deprecated. |
54 .sp |
53 Applications should use dynamically generated JRMP stubs, eliminating |
55 .nf |
54 the need to use the rmic tool for JRMP\-based applications. |
56 |
55 .PP |
57 \fBrmic\fR [ \fIoptions\fR ] \fIpackage\-qualified\-class\-names\fR |
56 The \f[CB]rmic\f[R] compiler generates stub and skeleton class files using |
58 .fi |
57 the JRMP. |
59 .sp |
58 .PP |
60 .TP |
59 \f[B]Note:\f[R] |
61 \fIoptions\fR |
60 .PP |
62 The command-line \f3options\fR\&. See Options\&. |
61 The rmic compiler has been updated to remove the \f[CB]\-idl\f[R] and |
63 .TP |
62 \f[CB]\-iiop\f[R] options and can no longer generate IDL or IIOP stubs and |
64 \fIpackage-qualified-class-names\fR |
63 tie classes. |
65 Class names that include their packages, for example, \f3java\&.awt\&.Color\fR\&. |
64 .PP |
66 .SH DESCRIPTION |
65 JRMP class files are generated from compiled Java programming language |
67 \fIDeprecation Note:\fR Support for static generation of Java Remote Method Protocol (JRMP) stubs and skeletons has been deprecated\&. Oracle recommends that you use dynamically generated JRMP stubs instead, eliminating the need to use this tool for JRMP-based applications\&. See the \f3java\&.rmi\&.server\&.UnicastRemoteObject\fR specification at http://docs\&.oracle\&.com/javase/8/docs/api/java/rmi/server/UnicastRemoteObject\&.html for further information\&. |
66 classes that are remote object implementation classes. |
68 .PP |
67 A remote implementation class is a class that implements the interface |
69 The \f3rmic\fR compiler generates stub and skeleton class files using the Java Remote Method Protocol (JRMP) and stub and tie class files (IIOP protocol) for remote objects\&. These class files are generated from compiled Java programming language classes that are remote object implementation classes\&. A remote implementation class is a class that implements the interface \f3java\&.rmi\&.Remote\fR\&. The class names in the \f3rmic\fR command must be for classes that were compiled successfully with the \f3javac\fR command and must be fully package qualified\&. For example, running the \f3rmic\fR command on the class file name \f3HelloImpl\fR as shown here creates the \f3HelloImpl_Stub\&.class\fRfile in the hello subdirectory (named for the class\&'s package): |
68 \f[CB]java.rmi.Remote\f[R]. |
70 .sp |
69 The class names in the \f[CB]rmic\f[R] command must be for classes that |
71 .nf |
70 were compiled successfully with the \f[CB]javac\f[R] command and must be |
72 \f3rmic hello\&.HelloImpl\fP |
71 fully package qualified. |
73 .fi |
72 For example, running the \f[CB]rmic\f[R] command on the class file name |
74 .nf |
73 \f[CB]HelloImpl\f[R] as shown here creates the |
75 \f3\fP |
74 \f[CB]HelloImpl_Stub.class\f[R] file in the \f[CB]hello\f[R] subdirectory |
76 .fi |
75 (named for the class\[aq]s package): |
77 .sp |
76 .RS |
78 A skeleton for a remote object is a JRMP protocol server-side entity that has a method that dispatches calls to the remote object implementation\&. |
77 .PP |
79 .PP |
78 \f[CB]rmic\ hello.HelloImpl\f[R] |
80 A tie for a remote object is a server-side entity similar to a skeleton, but communicates with the client with the IIOP protocol\&. |
79 .RE |
81 .PP |
80 .PP |
82 A stub is a client-side proxy for a remote object that is responsible for communicating method invocations on remote objects to the server where the actual remote object implementation resides\&. A client\&'s reference to a remote object, therefore, is actually a reference to a local stub\&. |
81 A skeleton for a remote object is a JRMP protocol server\-side entity |
83 .PP |
82 that has a method that dispatches calls to the remote object |
84 By default, the \f3rmic\fR command generates stub classes that use the 1\&.2 JRMP stub protocol version only, as though the \f3-v1\&.2\fR option was specified\&. The \f3-vcompat\fR option was the default in releases before 5\&.0\&. Use the \f3-iiop\fR option to generate stub and tie classes for the IIOP protocol\&. See Options\&. |
83 implementation. |
85 .PP |
84 .PP |
86 A stub implements only the remote interfaces, and not any local interfaces that the remote object also implements\&. Because a JRMP stub implements the same set of remote interfaces as the remote object, a client can use the Java programming language built-in operators for casting and type checking\&. For IIOP, the \f3PortableRemoteObject\&.narrow\fR method must be used\&. |
85 A stub is a client\-side proxy for a remote object that\[aq]s |
87 .SH OPTIONS |
86 responsible for communicating method invocations on remote objects to |
88 .TP |
87 the server where the actual remote object implementation resides. |
89 -bootclasspath \fIpath\fR |
88 A client\[aq]s reference to a remote object, therefore, is actually a |
90 .br |
89 reference to a local stub. |
91 Overrides the location of bootstrap class files\&. |
90 .PP |
92 .TP |
91 By default, the \f[CB]rmic\f[R] command generates stub classes that use |
93 -classpath path |
92 the 1.2 JRMP stub protocol version only, as though the \f[CB]\-v1.2\f[R] |
94 .br |
93 option were specified. |
95 Specifies the path the \f3rmic\fR command uses to look up classes\&. This option overrides the default or the \f3CLASSPATH\fR environment variable when it is set\&. Directories are separated by colons\&. The general format for path is: \f3\&.:<your_path>\fR, for example: \f3\&.:/usr/local/java/classes\fR\&. |
94 See \f[B]Options for the rmic Compiler\f[R]. |
96 .TP |
95 .PP |
97 -d \fIdirectory\fR |
96 A stub implements only the remote interfaces, and not local interfaces |
98 .br |
97 that the remote object also implements. |
99 Specifies the root destination directory for the generated class hierarchy\&. You can use this option to specify a destination directory for the stub, skeleton, and tie files\&. For example, the following command places the stub and skeleton classes derived from MyClass into the directory /java/classes/exampleclass\&. |
98 Because a JRMP stub implements the same set of remote interfaces as the |
100 .sp |
99 remote object, a client can use the Java programming language built\-in |
101 .nf |
100 operators for casting and type checking. |
102 \f3rmic \-d /java/classes exampleclass\&.MyClass\fP |
101 .PP |
103 .fi |
102 \f[B]Note:\f[R] |
104 .nf |
103 .PP |
105 \f3\fP |
104 The rmic compiler does not support reading of class files that have been |
106 .fi |
105 compiled with the \f[CB]\-\-enable\-preview\f[R] option, nor does it |
107 .sp |
106 support generation of stub or skeleton classes that have preview |
108 |
107 features enabled. |
109 |
108 .SH OPTIONS FOR THE RMIC COMPILER |
110 If the \f3-d\fR option is not specified, then the default behavior is as if \f3-d \&.\fR was specified\&. The package hierarchy of the target class is created in the current directory, and stub/tie/skeleton files are placed within it\&. In some earlier releases of the \f3rmic\fR command, if the \f3-d\fR option was not specified, then the package hierarchy was not created, and all of the output files were placed directly in the current directory\&. |
109 .TP |
111 .TP |
110 .B \f[CB]\-bootclasspath\f[R] \f[I]path\f[R] |
112 -extdirs \fIpath\fR |
111 Overrides the location of bootstrap class files. |
113 .br |
112 .RS |
114 Overrides the location of installed extensions\&. |
113 .RE |
115 .TP |
114 .TP |
116 -g |
115 .B \f[CB]\-classpath\f[R] \f[I]path\f[R] |
117 .br |
116 Specifies the path the \f[CB]rmic\f[R] command uses to look up classes. |
118 Enables the generation of all debugging information, including local variables\&. By default, only line number information is generated\&. |
117 This option overrides the default or the \f[CB]CLASSPATH\f[R] environment |
119 .TP |
118 variable when it is set. |
120 -idl |
119 Directories are separated by colons or semicolons, depending on your |
121 .br |
120 operating system. |
122 Causes the \f3rmic\fR command to generate OMG IDL for the classes specified and any classes referenced\&. IDL provides a purely declarative, programming language-independent way to specify an API for an object\&. The IDL is used as a specification for methods and data that can be written in and called from any language that provides CORBA bindings\&. This includes Java and C++ among others\&. See Java IDL: IDL to Java Language Mapping at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/mapping/jidlMapping\&.html |
121 The following is the general format for \f[I]path\f[R]: |
123 |
122 .RS |
124 When the \f3-idl\fR option is used, other options also include: |
123 .IP \[bu] 2 |
125 .RS |
124 \f[B]Oracle Solaris, Linux, and OS X:\f[R] |
126 .TP 0.2i |
125 \f[CB]\&.:\f[R]\f[I]your_path\f[R], for example: |
127 \(bu |
126 \f[CB]\&.:/usr/local/java/classes\f[R] |
128 The \f3-always\fR or \f3-alwaysgenerate\fR options force regeneration even when existing stubs/ties/IDL are newer than the input class\&. |
127 .IP \[bu] 2 |
129 .TP 0.2i |
128 \f[B]Windows:\f[R] \f[CB]\&.;\f[R]\f[I]your_path\f[R], for example: |
130 \(bu |
129 \f[CB]\&.;/usr/local/java/classes\f[R] |
131 The \f3-factory\fR option uses the \f3factory\fR keyword in generated IDL\&. |
130 .RE |
132 .TP 0.2i |
131 .TP |
133 \(bu |
132 .B \f[CB]\-d\f[R] \f[I]directory\f[R] |
134 The \f3-idlModule\fR from J\f3avaPackage[\&.class]\fR\f3toIDLModule\fR specifies \f3IDLEntity\fR package mapping, for example: \f3-idlModule\fR\f3my\&.module my::real::idlmod\fR\&. |
133 Specifies the root destination directory for the generated class |
135 .TP 0.2i |
134 hierarchy. |
136 \(bu |
135 You can use this option to specify a destination directory for the stub, |
137 \f3-idlFile\fR\f3fromJavaPackage[\&.class] toIDLFile\fR specifies \f3IDLEntity\fR file mapping, for example: \f3-idlFile test\&.pkg\&.X TEST16\&.idl\fR\&. |
136 skeleton, and tie files. |
138 .RE |
137 .RS |
139 |
138 .IP \[bu] 2 |
140 .TP |
139 \f[B]Oracle Solaris, Linux, and OS X:\f[R] For example, the following |
141 -iiop |
140 command places the stub and skeleton classes derived from |
142 .br |
141 \f[CB]MyClass\f[R] into the directory \f[CB]/java/classes/exampleclass\f[R]: |
143 Causes the \f3rmic\fR command to generate IIOP stub and tie classes, rather than JRMP stub and skeleton classes\&. A stub class is a local proxy for a remote object and is used by clients to send calls to a server\&. Each remote interface requires a stub class, which implements that remote interface\&. A client reference to a remote object is a reference to a stub\&. Tie classes are used on the server side to process incoming calls, and dispatch the calls to the proper implementation class\&. Each implementation class requires a tie class\&. |
142 .RS 2 |
144 |
143 .RS |
145 If you call the \f3rmic\fR command with the \f3-iiop\fR, then it generates stubs and ties that conform to this naming convention: |
144 .PP |
146 .sp |
145 \f[CB]rmic\ \-d\ /java/classes\ exampleclass.MyClass\f[R] |
147 .nf |
146 .RE |
148 \f3_<implementationName>_stub\&.class\fP |
147 .RE |
149 .fi |
148 .IP \[bu] 2 |
150 .nf |
149 \f[B]Windows:\f[R] For example, the following command places the stub and |
151 \f3_<interfaceName>_tie\&.class\fP |
150 skeleton classes derived from \f[CB]MyClass\f[R] into the directory |
152 .fi |
151 \f[CB]C:\\java\\classes\\exampleclass\f[R]: |
153 .nf |
152 .RS 2 |
154 \f3\fP |
153 .RS |
155 .fi |
154 .PP |
156 .sp |
155 \f[CB]rmic\ \-d\ C:\\java\\classes\ exampleclass.MyClass\f[R] |
157 .RS |
156 .RE |
158 .TP 0.2i |
157 .RE |
159 \(bu |
158 .PP |
160 When you use the \f3-iiop\fR option, other options also include: |
159 If the \f[CB]\-d\f[R] option isn\[aq]t specified, then the default |
161 .TP 0.2i |
160 behavior is as though \f[CB]\-d\f[R] was specified. |
162 \(bu |
161 The package hierarchy of the target class is created in the current |
163 The \f3-always\fR or \f3-alwaysgenerate\fR options force regeneration even when existing stubs/ties/IDL are newer than the input class\&. |
162 directory, and stub/tie/skeleton files are placed within it. |
164 .TP 0.2i |
163 .RE |
165 \(bu |
164 .TP |
166 The \f3-nolocalstubs\fR option means do not create stubs optimized for same-process clients and servers\&. |
165 .B \f[CB]\-g\f[R] |
167 .TP 0.2i |
166 Enables the generation of all debugging information, including local |
168 \(bu |
167 variables. |
169 The \f3-noValueMethods\fR option must be used with the \f3-idl\fR option\&. The \f3-noValueMethods\fR option prevents the addition of \f3valuetype\fR methods and initializers to emitted IDL\&. These methods and initializers are optional for valuetypes, and are generated unless the \f3-noValueMethods\fR option is specified with the \f3-idl\fR option\&. |
168 By default, only line number information is generated. |
170 .TP 0.2i |
169 .RS |
171 \(bu |
170 .RE |
172 The \f3-poa\fR option changes the inheritance from \f3org\&.omg\&.CORBA_2_3\&.portable\&.ObjectImpl\fR to \f3org\&.omg\&.PortableServer\&.Servant\fR\&. The \f3PortableServer\fR module for the Portable Object Adapter (POA) defines the native \f3Servant\fR type\&. In the Java programming language, the \f3Servant\fR type is mapped to the \f3Java org\&.omg\&.PortableServer\&.Servant\fR class\&. It serves as the base class for all POA servant implementations and provides a number of methods that can be called by the application programmer, and methods that are called by the POA and that can be overridden by the user to control aspects of servant behavior\&. Based on the OMG IDL to Java Language Mapping Specification, CORBA V 2\&.3\&.1 ptc/00-01-08\&.pdf\&..RE |
171 .TP |
173 |
172 .B \f[CB]\-J\f[R]\f[I]argument\f[R] |
174 .TP |
173 Used with any Java command, the \f[CB]\-J\f[R] option passes the |
175 -J |
174 \f[I]argument\f[R] that follows it (no spaces between the \f[CB]\-J\f[R] |
176 .br |
175 and the argument) to the Java interpreter. |
177 Used with any Java command, the \f3-J\fR option passes the argument that follows the \f3-J\fR (no spaces between the \f3-J\fRand the argument) to the Java interpreter |
176 .RS |
178 .TP |
177 .RE |
179 -keep or -keepgenerated |
178 .TP |
180 .br |
179 .B \f[CB]\-keep\f[R] or \f[CB]\-keepgenerated\f[R] |
181 Retains the generated \f3\&.java\fR source files for the stub, skeleton, and tie classes and writes them to the same directory as the\f3\&.class\fR files\&. |
180 Retains the generated \f[CB]\&.java\f[R] source files for the stub, |
182 .TP |
181 skeleton, and tie classes and writes them to the same directory as |
183 -nowarn |
182 the\f[CB]\&.class\f[R] files. |
184 .br |
183 .RS |
185 Turns off warnings\&. When the \f3-nowarn\fR options is used\&. The compiler does not print out any warnings\&. |
184 .RE |
186 .TP |
185 .TP |
187 -nowrite |
186 .B \f[CB]\-nowarn\f[R] |
188 .br |
187 Turns off warnings. |
189 Does not write compiled classes to the file system\&. |
188 When the \f[CB]\-nowarn\f[R] options is used, the compiler doesn\[aq]t |
190 .TP |
189 print warnings. |
191 -vcompat (deprecated) |
190 .RS |
192 .br |
191 .RE |
193 Generates stub and skeleton classes that are compatible with both the 1\&.1 and 1\&.2 JRMP stub protocol versions\&. This option was the default in releases before 5\&.0\&. The generated stub classes use the 1\&.1 stub protocol version when loaded in a JDK 1\&.1 virtual machine and use the 1\&.2 stub protocol version when loaded into a 1\&.2 (or later) virtual machine\&. The generated skeleton classes support both 1\&.1 and 1\&.2 stub protocol versions\&. The generated classes are relatively large to support both modes of operation\&. Note: This option has been deprecated\&. See Description\&. |
192 .TP |
194 .TP |
193 .B \f[CB]\-nowrite\f[R] |
195 -verbose |
194 Doesn\[aq]t write compiled classes to the file system. |
196 .br |
195 .RS |
197 Causes the compiler and linker to print out messages about what classes are being compiled and what class files are being loaded\&. |
196 .RE |
198 .TP |
197 .TP |
199 -v1\&.1 (deprecated) |
198 .B \f[CB]\-vcompat\f[R] (deprecated) |
200 .br |
199 Generates stub and skeleton classes that are compatible with both the |
201 Generates stub and skeleton classes for the 1\&.1 JRMP stub protocol version only\&. The \f3-v1\&.1\fR option is only useful for generating stub classes that are serialization-compatible with preexisting, statically deployed stub classes that were generated by the \f3rmic\fR command from JDK 1\&.1 and that cannot be upgraded (and dynamic class loading is not being used)\&. Note: This option has been deprecated\&. See Description\&. |
200 1.1 and 1.2 JRMP stub protocol versions. |
202 .TP |
201 This option was the default in releases before 5.0. |
203 -v1\&.2 (deprecated) |
202 The generated stub classes use the 1.1 stub protocol version when loaded |
204 .br |
203 in a JDK 1.1 virtual machine and use the 1.2 stub protocol version when |
205 (Default) Generates stub classes for the 1\&.2 JRMP stub protocol version only\&. No skeleton classes are generated because skeleton classes are not used with the 1\&.2 stub protocol version\&. The generated stub classes do not work when they are loaded into a JDK 1\&.1 virtual machine\&. Note: This option has been deprecated\&. See Description\&. |
204 loaded into a 1.2 (or later) virtual machine. |
206 .SH ENVIRONMENT\ VARIABLES |
205 The generated skeleton classes support both 1.1 and 1.2 stub protocol |
207 .TP |
206 versions. |
208 CLASSPATH |
207 The generated classes are relatively large to support both modes of |
209 Used to provide the system a path to user-defined classes\&. Directories are separated by colons, for example: \f3\&.:/usr/local/java/classes\fR\&. |
208 operation. |
210 .SH SEE\ ALSO |
209 .RS |
211 .TP 0.2i |
210 .PP |
212 \(bu |
211 \f[B]Note:\f[R] |
213 javac(1) |
212 .PP |
214 .TP 0.2i |
213 This option has been deprecated. |
215 \(bu |
214 See \f[B]Description\f[R]. |
216 java(1) |
215 .RE |
217 .TP 0.2i |
216 .TP |
218 \(bu |
217 .B \f[CB]\-verbose\f[R] |
219 Setting the Class Path |
218 Causes the compiler and linker to print messages about what classes are |
220 .RE |
219 being compiled and what class files are being loaded. |
221 .br |
220 .RS |
222 'pl 8.5i |
221 .RE |
223 'bp |
222 .TP |
|
223 .B \f[CB]\-v1.1\f[R] (deprecated) |
|
224 Generates stub and skeleton classes for the 1.1 JRMP stub protocol |
|
225 version only. |
|
226 The \f[CB]\-v1.1\f[R] option is useful only for generating stub classes |
|
227 that are serialization\-compatible with existing, statically deployed |
|
228 stub classes generated by the \f[CB]rmic\f[R] command from JDK 1.1 that |
|
229 can\[aq]t be upgraded (and dynamic class loading isn\[aq]t being used). |
|
230 .RS |
|
231 .PP |
|
232 \f[B]Note:\f[R] |
|
233 .PP |
|
234 This option has been deprecated. |
|
235 See \f[B]Description\f[R]. |
|
236 .RE |
|
237 .TP |
|
238 .B \f[CB]\-v1.2\f[R] (deprecated) |
|
239 (Default) Generates stub classes for the 1.2 JRMP stub protocol version |
|
240 only. |
|
241 No skeleton classes are generated because skeleton classes aren\[aq]t |
|
242 used with the 1.2 stub protocol version. |
|
243 The generated stub classes don\[aq]t work when they\[aq]re loaded into a |
|
244 JDK 1.1 virtual machine. |
|
245 .RS |
|
246 .PP |
|
247 \f[B]Note:\f[R] |
|
248 .PP |
|
249 This option has been deprecated. |
|
250 See \f[B]Description\f[R]. |
|
251 .RE |
|
252 .SH ENVIRONMENT VARIABLES |
|
253 .TP |
|
254 .B \f[CB]CLASSPATH\f[R] |
|
255 Used to provide the system a path to user\-defined classes. |
|
256 .RS |
|
257 .IP \[bu] 2 |
|
258 \f[B]Oracle Solaris, Linux, and OS X:\f[R] Directories are separated by |
|
259 colons, for example: \f[CB]\&.:/usr/local/java/classes\f[R]. |
|
260 .IP \[bu] 2 |
|
261 \f[B]Windows:\f[R] Directories are separated by colons, for example: |
|
262 \f[CB]\&.;C:\\usr\\local\\java\\classes\f[R]. |
|
263 .RE |