Looks like a left-over from the various class movements:
-
the package name of the sql-proto project is sql.plugin. This is incorrect and misleading since that's the package of the server. It should be changed to something more appropriate like sql.proto or (to avoid a cycle with 2 below) `sql.proto.action.
-
the package name of the shared-proto project is sql.proto. Due to 1 above, it should be sql.proto.shared or (since that creates a cycle between proto.shared and proto) to sql.shared.proto or sql.proto.common .
That is, the package name should properly convey the project name and the hierarchy (sql-proto depends on shared-proto not vice versa) without splitting an existing package name.
Looks like a left-over from the various class movements:
the package name of the
sql-protoproject issql.plugin. This is incorrect and misleading since that's the package of the server. It should be changed to something more appropriate likesql.protoor (to avoid a cycle with 2 below) `sql.proto.action.the package name of the shared-proto project is
sql.proto. Due to 1 above, it should besql.proto.sharedor (since that creates a cycle betweenproto.sharedandproto) tosql.shared.protoorsql.proto.common.That is, the package name should properly convey the project name and the hierarchy (
sql-protodepends onshared-protonot vice versa) without splitting an existing package name.