This document is about configuring Gerrit Code Review into an Eclipse workspace for development and debugging with GWT.
Java 6 or later SDK is also required to run GWT's compiler and runtime debugging environment.
Install the Maven Integration plugins:
Import tools/GoogleFormat.xml using Window -> Preferences -> Java -> Code Style -> Formatter -> Import…
This will define the Google Format profile, which the project settings prefer when formatting source code.
Import the projects into Eclipse by going to File -> Import… -> Maven -> Existing Maven Projects and selecting the directory containing pom.xml.
Some of the source code is generated with ANTLR sources. To build these files, right click on the imported projects, Maven -> Update Project Configuration. This will resolve compile errors identified after import.
Build once on the command line and then follow Site Initialization in the Developer Setup guide to configure a local site for testing.
Duplicate the existing pgm_daemon launch configuration:
Run -> Debug Configurations …
Java Application -> pgm_daemon
Right click, Duplicate
Modify the name to be unique.
Switch to Arguments tab.
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.
Import the gerrit-gwtdebug project:
Import gerrit-gwtdebug/pom.xml using General -> Maven Projects
Duplicate the existing gwtui_dbg launch configuration:
Run -> Debug Configurations …
Java Application -> gwtui_dbg
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.
Part of Gerrit Code Review