Github user karensmolermiller commented on a diff in the pull request:
https://github.com/apache/geode/pull/635#discussion_r127524976
--- Diff: geode-docs/configuring/running/running_the_locator.html.md.erb ---
@@ -35,7 +35,7 @@ You can run the locator standalone or embedded within
another Geode process. Run
Locator configuration and log files have the following properties:
-- When you start a standalone locator using `gfsh`, `gfsh` will
automatically load the required JAR files
(`$GEMFIRE/lib/locator-dependencies.jar`) into the CLASSPATH of the JVM
process. If you start a standalone locator using the `LocatorLauncher` API, you
must specify `$GEMFIRE/lib/locator-dependencies.jar` inside the command used to
launch the locator process. For more information on CLASSPATH settings in
Geode, see [CLASSPATH Settings for Geode
Processes](../../getting_started/setup_classpath.html). You can modify the
CLASSPATH by specifying the `--classpath` parameter.
+- When you start a standalone locator using `gfsh`, `gfsh` will
automatically load the required JAR file
(`$GEMFIRE/lib/locator-dependencies.jar`) into the CLASSPATH of the JVM
process. If you start a standalone locator using the `LocatorLauncher` API, you
must specify `$GEMFIRE/lib/locator-dependencies.jar` inside the command used to
launch the locator process. For more information on CLASSPATH settings in
Geode, see [CLASSPATH Settings for Geode
Processes](../../getting_started/setup_classpath.html). You can modify the
CLASSPATH by specifying the `--classpath` parameter.
--- End diff --
That task is being tracked with Geode-3208.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
