Completely remove GerritServer.properties
We now load our database settings in hosted development mode from
the $site_path/etc/gerrit.config, just like we would under daemon.
This reduces the number of weird configurations that are supported.
Change-Id: I0a13f16dd74bdb034d05650eadd5e36771109f3e
Signed-off-by: Shawn O. Pearce <sop@google.com>
diff --git a/Documentation/dev-eclipse.txt b/Documentation/dev-eclipse.txt
index 81c5ae6..dab246b 100644
--- a/Documentation/dev-eclipse.txt
+++ b/Documentation/dev-eclipse.txt
@@ -82,9 +82,9 @@
* Modify the name to be unique.
* Switch to Arguments tab.
-* Edit the -d flag to match the path used during 'init'. The
- template launch configuration resolves to ../test_site since
- that is what the documentation recommends.
+* Edit the `-d` program argument flag to match the path used during
+ 'init'. The template launch configuration resolves to ../test_site
+ since that is what the documentation recommends.
* Switch to Common tab.
* Change Save as to be Local file.
@@ -93,12 +93,22 @@
Running Hosted Mode
~~~~~~~~~~~~~~~~~~~
-* Copy
- `gerrit-war/src/main/webapp/WEB-INF/extra/GerritServer.properties_example`
- to
- `gerrit-parent/GerritServer.properties`.
-* Edit to match your database parameters.
-* Run the `gwtui_any` or `gwtui_mac` launch configuration.
+Duplicate the existing `gwtui_any` (or `gwtui_mac` if on Mac OS X)
+launch configuration:
+
+* Run -> Debug Configurations ...
+* Java Application -> `gwtui_any`
+* Right click, Duplicate
+
+* Modify the name to be unique.
+
+* Switch to Arguments tab.
+* Edit the `-Dgerrit.site_path=` VM argument to match the path
+ used during 'init'. The template launch configuration resolves
+ to ../test_site since that is what the documentation recommends.
+
+* Switch to Common tab.
+* Change Save as to be Local file.
GERRIT
