[
https://issues.apache.org/jira/browse/SOLR-18234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080400#comment-18080400
]
David Smiley commented on SOLR-18234:
-------------------------------------
"solr-core" is our largest gradle [sub]project Reducing its scope is helpful.
I know such a change won't bring about some big win but I find there to be nice
intangibles to breaking up large projects on boundaries that make some sense.
> core-cli build module
> ---------------------
>
> Key: SOLR-18234
> URL: https://issues.apache.org/jira/browse/SOLR-18234
> Project: Solr
> Issue Type: Task
> Reporter: David Smiley
> Priority: Major
>
> The "org.apache.solr.cli" package ought to be separated to a module (gradle
> sub-project), e.g. "core-cli", adjacent to "core". Motivation: reduce
> dependencies of solr-core[1], and reduces the size/scope of our largest
> module[2].
> [1]: even though Solr will certainly ship with this JAR and its dependencies:
> (a) they won't go/belong in WEB-INF/lib and won't be on Solr's runtime
> classpath, (b) anyone embedding Solr-core won't need CLI or its dependencies,
> and (c) also applies to users of solr-test-framework
> [2]: The gradle build can run a bit more efficiently when our largest
> sub-project is reduced in size for a variety of reasons
> [3]: new dirs are likely useful for misc things like an AGENTS.md, README.md,
> maybe referencing in CODEOWNERS and misc things.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
