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:
@@ -26,10 +26,10 @@ import com.google.common.io.Files;
|
||||
import com.google.gerrit.elasticsearch.ElasticAccountIndex.AccountMapping;
|
||||
import com.google.gerrit.elasticsearch.ElasticChangeIndex.ChangeMapping;
|
||||
import com.google.gerrit.elasticsearch.ElasticGroupIndex.GroupMapping;
|
||||
import com.google.gerrit.index.Schema;
|
||||
import com.google.gerrit.reviewdb.client.AccountGroup;
|
||||
import com.google.gerrit.server.account.AccountState;
|
||||
import com.google.gerrit.server.index.IndexModule.IndexType;
|
||||
import com.google.gerrit.server.index.Schema;
|
||||
import com.google.gerrit.server.index.account.AccountSchemaDefinitions;
|
||||
import com.google.gerrit.server.index.change.ChangeSchemaDefinitions;
|
||||
import com.google.gerrit.server.index.group.GroupSchemaDefinitions;
|
||||
|
Reference in New Issue
Block a user