Rewrite our build as modular maven components
This refactoring splits the code up into different components, with
their own per-component CLASSPATH. By moving all of our classes
into isolated components we can better isolate the classpaths and
try to avoid unexpected dependency problems. It also allows us to
more clearly define which components are used by the GWT UI and
thus must be compiled under GWT, and which components are run on
the server and can therefore use more of the J2SE API.
Change-Id: I833cc22bacc5655d1c9099ed7c2b0e0a5b08855a
Signed-off-by: Shawn O. Pearce <sop@google.com>
diff --git a/Documentation/dev-readme.txt b/Documentation/dev-readme.txt
index e0e2017..6748322 100644
--- a/Documentation/dev-readme.txt
+++ b/Documentation/dev-readme.txt
@@ -43,8 +43,7 @@
and then configure your workspace anyway).
====
- cd src/main/java
- cp GerritServer.properties_example GerritServer.properties
+ cp gerrit-war/src/main/webapp/WEB-INF/extra/GerritServer.properties_example GerritServer.properties
====
Now edit GerritServer.properties to uncomment the database you are
@@ -104,7 +103,7 @@
Output WAR will be placed in:
====
- target/gerrit-*.war
+ gerrit-war/target/gerrit-*.war
====
When debugging browser specific issues use gwtStyle `DETAILED` so
