[
https://issues.apache.org/jira/browse/SOLR-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645187#comment-14645187
]
Timothy Potter commented on SOLR-7043:
--------------------------------------
bq. Separately, I've been thinking a little bit about the solr.in.* scripts, if
we choose to continue using bash/batch. Some of the documentation suggests
editing those for customization, but I don't think that's a good idea.
[~elyograg] that's a separate issue than this ... please open a JIRA for that
so it can be discussed / worked on separately
> Refactor SolrCLI, bin\solr, bin\solr.cmd to be more unit-testable and less OS
> specific
> --------------------------------------------------------------------------------------
>
> Key: SOLR-7043
> URL: https://issues.apache.org/jira/browse/SOLR-7043
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Reporter: Timothy Potter
> Assignee: Timothy Potter
>
> With the 5.0 release, we've reached critical mass with the bin/solr script
> interface, but we've picked up some cruft along the way. Specifically,
> there's too much OS-specific constructs in the scripts and they are quite
> complex overall. They also require extensive manual testing. Moreover,
> SolrCLI (provides support for the scripts) needs to be refactored to use the
> Collections API support added to SolrJ instead of using low-level JSON / HTTP
> constructs. SolrCLI is also in desperate need of a unit test. The overall
> goal of this ticket is to move as much as possible out of the shell scripts
> and into SolrCLI, thus increasing test coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
