Move general index classes from gerrit-server to gerrit-index
These classes do not depend on any Gerrit server functionality, and could even be used to define an index without depending on the gerrit-server package. This allows for a clearer separation of BUILD rules; the QueryParser and antlr targets don't escape the gerrit-index package. The general layout thus far is to put index definition code in com.google.gerrit.index, and query-related code (predicates, etc.) in com.google.gerrit.index.query. The gerrit-index package is still of limited utility on its own, because QueryProcessor and InternalQuery still live in the server package, and untangling their dependencies will still be a bit more work. Change-Id: I3c4616d08ecf19d5ccd1b9b91b3fd0b1fcedd901
This commit is contained in:
@@ -7,6 +7,7 @@ PROVIDED = [
|
||||
"//gerrit-common:server",
|
||||
"//gerrit-extension-api:api",
|
||||
"//gerrit-httpd:httpd",
|
||||
"//gerrit-index:index",
|
||||
"//gerrit-lucene:lucene",
|
||||
"//gerrit-pgm:init",
|
||||
"//gerrit-reviewdb:server",
|
||||
|
@@ -14,13 +14,13 @@
|
||||
|
||||
package com.google.gerrit.acceptance;
|
||||
|
||||
import com.google.gerrit.index.QueryOptions;
|
||||
import com.google.gerrit.index.Schema;
|
||||
import com.google.gerrit.index.query.DataSource;
|
||||
import com.google.gerrit.index.query.Predicate;
|
||||
import com.google.gerrit.index.query.QueryParseException;
|
||||
import com.google.gerrit.reviewdb.client.Change.Id;
|
||||
import com.google.gerrit.server.index.QueryOptions;
|
||||
import com.google.gerrit.server.index.Schema;
|
||||
import com.google.gerrit.server.index.change.ChangeIndex;
|
||||
import com.google.gerrit.server.query.DataSource;
|
||||
import com.google.gerrit.server.query.Predicate;
|
||||
import com.google.gerrit.server.query.change.ChangeData;
|
||||
import java.io.IOException;
|
||||
|
||||
|
Reference in New Issue
Block a user