d064abea4f
Encapsulate the current state of the migration in a NotesMigration class. For each database table (or broader group of functionality) that we migrate to notedb, configure a boolean indicating whether that data should be read from notes, defaulting to false. Unlike reads, NotesMigration contains just a single boolean indicating that data should be written. We don't attempt to write just some types of data; as the migration continues we will just rewrite history. Since most existing reads of the PatchSetApprovals table have been migrated to ApprovalsUtil, most implementation changes happen there. There are a few other implementations scattered around, and some that will require a bit more work (e.g. stamping normalized approvals at submit time). Change-Id: I5676267d4de607c385e8c9917a89333863b9c9e7
If you are adding a directory here: - Search all pom.xml files for "CORE PLUGIN LIST". - Add the new plugin to that location. - (optional) Thank the Maven developers for making this easy. - Ensure the plugin's pom.xml <version> is the same as Gerrit's own pom.xml(s). Gerrit will only embed a plugin that has the same version as itself. - Register the plugin as a submodule with git submodule.